Hello, there is currently no chance to get the peer IP from the client. But it would be easy to implement when needed. At least on http level.
On xmlrpc level the server calls a function. And the function do not have any context, where it can ask for additional information. I don't know, how to pass that information. For a session system it might be better to implement your own rpc function for that like a login method, which returns an ID. Sessions are not part of the xmlrpc standard and when we implement something like a session system based on cookies for example, we leave the xmlrpc standard. I'm currently working on a binary rpc. Maybe I should implement a session system there. This is purely propritary anyway. Tommi ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ Tntnet-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tntnet-general
