Re: [jboss-dev] Remoting 3.0
Hi Carlo,
I'm not sure I understand what you're asking for. An
org.jboss.remoting.Client has an identity, the sessionId, which is
included in the InvocationRequest. But Client doesn't really map to an
InetAddress. The socket transport, for example, maintains a pool of TCP
connections, each with a different port. Remoting could supply the
InetAddress of the connection used for a particular invocation, if
that's what you mean. But note that that same connection could be used
by a different Client for a different invocation at any time.
-Ron
Carlo de Wolf wrote:
I would like to see the client endpoint (InetAddress most of the
time)
of an invocation. Maybe it's already in the InvocationRequest, but I
can't find it.
Carlo
On Thu, 2007-05-17 at 15:51 -0400, Ron Sigal wrote:
> There have been various attempts to get some discussion going about the
> features desired for the next generation of Remoting, and so far I think
> the buzz has broken the -80 db level. I'm trying again with the wiki
> page at
> http://wiki.jboss.org/wiki/Wiki.jsp?page=TowardsGreaterSymmetryInRemoting.
> We in the Remoting group (i.e., me in the Remoting group) would like to
> hear from the Remoting stakeholders about what features would make
> Remoting more usable for you. Of course, I could just go ahead and
> write fun stuff. :-)
>
> -Ron
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
Attachments:
- attachment.html (text/html — 2.6 KB)