Don't have an account yet? Go Create One. A user account will let you customize the site's content according to your preferences. It will also allow you to moderate the comments of other users.
by Greg Weiss on Wednesday October 03, @08:24AM EST (#1)
(User #10 Info)
XML makes sense for passing data around or storing it, unless your application has unusual space constraints. Still, I'd be curious what other people think of using XML-RPC for over-the-wire XML communication protocols.
Do we need RPC for XML already on top of TCP/IP? When a company I worked with suggested replacing an xml interface we were using with XML-RPC ("it's the big standard going forward") and I looked at the specifics of the XML traffic we'd be switching to, the ensuing XML ACK and NO_ACK responses sent back and for seemed to generate a surprisingly large (~10x in our case) increase in network traffic and number of connections required. I'm sure we could have optimized some of that away but I found myself asking "why bother?" Has anyone else looked at XML-RPC and found that the extra traffic was worth it? Or not?
--Greg
P.S. Beware subject lines in all caps like "XML-RPC"... the Slash software thinks they are lame yelling (no wonder slashdot is less technical these days!)
