[jboss-dev] Remoting 3.0
Carlo de Wolf
carlo.dewolf at jboss.com
Tue Jun 19 03:05:06 EDT 2007
http://jira.jboss.com/jira/browse/JBREM-758
Carlo
On Mon, 2007-06-18 at 19:12 -0400, Ron Sigal wrote:
> For the socket transport and its descendants (sslsocket, bisocket,
> sslbisocket), we can get the remote address and add it to the
> requestPayload Map in the InvocationRequest. For the http transport,
> it looks like we can also get the remote address from the
> org.apache.coyote.Request, but I haven't verified that. I don't think
> we can get access to the remote address in the rmi transport.
>
> Would you like to create a JIRA issue? Otherwise, assuming I
> understand you now, I will.
>
> -Ron
>
> Carlo de Wolf wrote:
> > No I mean the remote socket address:
> > http://java.sun.com/j2se/1.5.0/docs/api/java/net/Socket.html#getRemoteSocketAddress()
> >
> > Somewhere deep down if a remote invocation comes in over a socket the
> > remote address is known. If it can be associated with the invocation it
> > can be used to set up auditing and filtering.
> >
> > Carlo
> >
> > On Sun, 2007-06-17 at 03:46 -0400, Ron Sigal wrote:
> >
> > > 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 at lists.jboss.org
> > > > > https://lists.jboss.org/mailman/listinfo/jboss-development
> > > > >
> > > > >
> > > > _______________________________________________
> > > > jboss-development mailing list
> > > > jboss-development at lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/jboss-development
> > > >
> > > >
> > > _______________________________________________
> > > jboss-development mailing list
> > > jboss-development at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/jboss-development
> > >
> >
> > _______________________________________________
> > jboss-development mailing list
> > jboss-development at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jboss-development
> >
>
> --
> JBoss, a Division of Red Hat
> "My company's smarter than your company."
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
More information about the jboss-development
mailing list