I am application which needs gain access to the client IP / port. I'd rather not have to include in the arguments to the xmlrpc method, but would rather have it come from the receiving socket itself.

At a quick glance, it seems like access to the underlying transport could be included in the XmlRpcContext class. This might provide users with the ability to access this information.

So, anyone have some suggestions on how this can be done or must I dive in and do it? Let me know if you think this discussion should be taken to the -dev list.

Thanks,

-jr

Reply via email to