Hiram Chirino wrote:
Hiram Chirino wrote:
> Anyways.  JMS need bi-directional invocations (BADLY).  Should this
> become a requirement for the other invokers??

I completely disagree.  There is no reason server to client
communication has to go over the back channel of a client to server

I might have said this before, but there is one reason it's a nice feature:
This allows callback to clients that are sitting behind a firewall.
Yes but it should not be required.

invoker.  It is a nice feature but should not be a requirement.  For
example, I may want a system that uses RMI for client to server and
Juxta for server to client.  To me it is just another RPC.  This is why
I want JMX on the client side, so I can reuse any invoker for the server
to client (or client to client) communication.

Yep.. I guess that's what I'm complaining about.  I want to have invokers on
the client side too.  I want JMS call backs to go via an invoker too.  I
can't do that today because we don't do client side invokers.
This is why I want jmx on the client side. We should be able to use any of our invokers for the back channel (unless there is a firewall).

-dain



-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to