Hello,
I'm writting a client/server game where I want the
client to be able to call methods on the server, and
for the server to call methods on the client to notify
it that the other player has moved, etc. The clients
may be behind a firewall, etc. so I don't want the
client to open a serversocket. I believe your
implementation wouldn't allow for this as the
XmlRpcClient... classes take URL and connection info.
So I changed some things for this to work.
The goal is to have the client connect to the server
twice creating 2 sockets, one for the client->server
rpc calls and the other for the server->client rpc
calls and use your xmlrpc functionality over them.
I extended the WebServer class so it takes a socket
and reimplemented the WebServer.Connection class to
handle reuse and other junk, but basically it takes a
socket and accepts calls. Then I modified the
XmlRpcClientLite and LiteXmlRpcTransport classes to
take a sockets as well and use them internally.
That's basically it.
Does this make sense and are there other/better ways
to do this? And if this is not a stupid idea, i could
provide the code.
Thanks
__________________________________
Do you Yahoo!?
Yahoo! Mail - 250MB free storage. Do more. Manage less.
http://info.mail.yahoo.com/mail_250
