I agree. The port is subject to change, but the IP should remain the
same. (or at least in my application it will) I think this information
could be as useful as the userid/password. Other information which could
be useful could be the client certificate information if the connection
is SSL and a client certificate was presented. This could allow the rpc
method to do authentication/authorization based on that data too.
Jochen Wiedmann wrote:
> James Russo wrote:
>> I am application which needs gain access to the client IP / port.
> There is no such thing as *the* client IP / port. Even with HTTP
> keepalive you have to accept the possibility, that different XML-RPC
> requests use different ports. (The IP address is likely to be
> constant, though.)