RE: So what do SOAP and XML-RPC buy you? (was Re: Massive Cross-P ost:The State of XML-RPC, April 2001)

["Bullard, Claude L (Len)" <clbullar@ingr.com>]

Ummm.... idiot question.  Do I really want to send anyObject 
and marshall/unmarshall that, or just a message?  It seems 
in the past that when one starts sending anyObject, a hairball 
of dependencies is incurred.   This makes the scheme 
something possibly heavier than what is wanted.   At 
what point am I packing up a very big hairball and trying 
to mail it to a receiver when really, I want them to do 
a bit of work by request and send me the results, not 
create an exe and mail it back.  In other words, where 
does service and persistence blur?

Len 
http://www.mp3.com/LenBullard

Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h


-----Original Message-----
From: Matt Sergeant [mailto:matt@sergeant.org]

> Specifically, what is missing is that you can't do:
>
>   http.put(url, anyObject)
>
> and have 'anyObject' marshalled and serialized to XML automatically by
> the library, and then sent over HTTP.

But that's a factor of the library you use for SOAP/XMLRPC, not a factor
of XMLRPC or SOAP itself. You could just as easily write an
auto-marshalling module that does this without the SOAP envelope formats.

You still have to negitiate with the reciever exactly what formats and
parameters you can send/recieve.