Streaming XML-RPC?

Jeremy Bowers newsfroups at jerf.org
Tue Mar 26 23:28:56 EST 2002


Magnus Lie Hetland wrote:
> In article <3C9F51EE.5000203 at jerf.org>, Jeremy Bowers wrote:
>>This is in stark contrast to HTTP. HTTP thinks you're nuts. HTTP will 
>>fight you tooth and nail. HTTP is old, and hoary, and set in her ways. 
>>And XML-RPC isn't exactly ecstatic about being streamed, either.


> Well, jabber-rpc is just XML-RPC in a Jabber stream... :)

Yes, but it goes out in discrete chunks. Watch a jabber-rpc call, and 
and XML-RPC call, go by on the wire, and they'll look the same modulo 
some header.

Try to trickle XML-RPC calls over either system and it'll be ugly. 
(Uglier in Jabber, though, because you'll be consuming the entire Jabber 
connection while you're trying that.)

If you have control of both the server and the client, you may be able 
to set up an ugly fast RPC server. Just have it look for <methodCall> 
and </methodCall> while reading a TCP stream, and break the stream up 
that way. (Watch out to make sure that the server always responds in 
order, or tag them with ids.)




More information about the Python-list mailing list