You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2011/01/27 14:46:50 UTC
DO NOT REPLY [Bug 50670] Tribes | RpcChannel | Add option to specify
external class loaders to support custom message classes
https://issues.apache.org/bugzilla/show_bug.cgi?id=50670
--- Comment #1 from Olivier Costet <oc...@zenprise.com> 2011-01-27 08:46:47 EST ---
Reproducing comments from
https://issues.apache.org/bugzilla/show_bug.cgi?id=50648:
Filip Hanik wrote:
> 3.
> The external loaders IMHO don't belong here.
> For the applications that wish to provide custom class loading, I would simply
> send messages using the ByteMessage class. That way you have full control over
> what is happening.
It's true, you could use ByteMessages. Although as an API user, your code would
become more clunky, and you'd lose the ability to quickly look up the message's
class.
Wouldn't it be nice to have, though? It makes things easier, cleaner and
doesn't add any significant overhead. Also, as things stand, the tribes API is
somewhat misleading in that it offers to send Serializable messages (methods
like Channel#send take Serializable arguments), when in practice all your app's
classes are excluded, no matter how Serializable they may be.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org