Approaches of interprocess communication
Diez B. Roggisch
deets at nospam.web.de
Fri Feb 16 08:53:27 EST 2007
More information about the Python-list mailing list
Fri Feb 16 08:53:27 EST 2007
- Previous message (by thread): Approaches of interprocess communication
- Next message (by thread): Approaches of interprocess communication
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Paul Boddie wrote: > On 16 Feb, 14:16, "Diez B. Roggisch" <d... at nospam.web.de> wrote: >> >> You can't leave WSDL out of SOAP > > Yes you can, since they're two different things. What you probably > meant was that you can't leave WSDL out of "big architecture", W3C > standards-intensive Web services. Of course, RPC-style SOAP without > the contracts imposed by WSDL may remove some of the attractions for > some people (who really should consider CORBA, anyway), but then > there's always document-oriented SOAP, although if you don't want the > baggage associated with routing and other things, plain XML messaging > would be easier. And there's always XMPP if you want stuff like > routing and a standard that isn't undergoing apparently continuous > change. Didn't know that. Yet I presume it is pretty awful to manually decompose and compose the method invocations and parameter sets. I've got no idea what document-orientied SOAP means either. Is that just pushing XML-files over a protocol? Diez
- Previous message (by thread): Approaches of interprocess communication
- Next message (by thread): Approaches of interprocess communication
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list