Comments on: Tubularity http://www.xmlgrrl.com/blog/archives/2005/04/02/tubularity/ XML, identity, crafting, and other tangled musings Fri, 21 Nov 2008 06:20:50 +0000 http://wordpress.org/?v=2.5 By: Eve M. http://www.xmlgrrl.com/blog/archives/2005/04/02/tubularity/#comment-318 Eve M. Tue, 17 May 2005 23:38:38 +0000 http://www.xmlgrrl.com/blog/archives/2005/04/02/tubularity/#comment-318 Hi John! You're right that it's more elegant, but it makes an assumption that the new higher SOAP layer is deployed everywhere (or at least in more places than HTTP is), which is a bit of a leap. There's no problem that another layer of abstraction can't make more resource-intensive...uh, rather...solve. Hi John! You’re right that it’s more elegant, but it makes an assumption that the new higher SOAP layer is deployed everywhere (or at least in more places than HTTP is), which is a bit of a leap. There’s no problem that another layer of abstraction can’t make more resource-intensive…uh, rather…solve.

]]> By: John Kemp http://www.xmlgrrl.com/blog/archives/2005/04/02/tubularity/#comment-317 John Kemp Tue, 17 May 2005 20:58:54 +0000 http://www.xmlgrrl.com/blog/archives/2005/04/02/tubularity/#comment-317 Hi Eve, I don't think anyone must use SOAP. Particularly if your XML services are already ONLY exposed over HTTP/IP. But what if you don't have an HTTP server, and/or you want to receive messages over some other transport (perhaps without any "transport-layer" headers)? One alternative would be to put everything in the body of the message, but that doesn't seem to be a good architecture if you want to run multiple services. The SOAP header abstraction enables things that don't currently have full HTTPDs running,and may not have such things for some time, to provide XML-based services. Talk about extending your reach ;) Wouldn't you agree that this is more elegant than putting potentially duplicated information into an application message? Hi Eve,

I don’t think anyone must use SOAP. Particularly if your XML services are already ONLY exposed over HTTP/IP. But what if you don’t have an HTTP server, and/or you want to receive messages over some other transport (perhaps without any “transport-layer” headers)? One alternative would be to put everything in the body of the message, but that doesn’t seem to be a good architecture if you want to run multiple services. The SOAP header abstraction enables things that don’t currently have full HTTPDs running,and may not have such things for some time, to provide XML-based services. Talk about extending your reach ;) Wouldn’t you agree that this is more elegant than putting potentially duplicated information into an application message?

]]>