tag:blogger.com,1999:blog-8655567.post114400966948467634..comments2023-10-30T01:48:47.905-07:00Comments on Panic From Fuzzy: SOAP is the backbone - REST/POX is the eject buttonfuzzyhttp://www.blogger.com/profile/04442788840388847156noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-8655567.post-1149948347667883922006-06-10T07:05:00.000-07:002006-06-10T07:05:00.000-07:00Thanks for the comment Elliot!I have worked with S...Thanks for the comment Elliot!<BR/><BR/>I have worked with SOAP since it came out. I do all of the complex things you mentioned and still avoid it like the plague.<BR/><BR/>SOAP makes none of these things easier. On the contrary, it makes them more difficult in my experience.<BR/><BR/>Cheers.fuzzyhttps://www.blogger.com/profile/04442788840388847156noreply@blogger.comtag:blogger.com,1999:blog-8655567.post-1149947047170379562006-06-10T06:44:00.000-07:002006-06-10T06:44:00.000-07:00Headers residing within a SOAP message may seem we...Headers residing within a SOAP message may seem weird at first to those not familiar with web services standards, but there is much value in allowing header information to be exposed in such a way.<BR/><BR/>SOAP over HTTP isn't really an ideal way to be performing large numbers of operations over a network; it's (ab)using HTTP in a manner that wasn't the intended purpose of the protocol. SOAP over HTTP (or REST over HTTP, for that matter) is not an efficient usage of the underlying TCP protocol for scenarios involving significant message volumes..<BR/><BR/>Allowing headers to reside within the SOAP Message XML pulls away from existing solutions' underlying focus on HTTP, allowing future integration solutions to run overtop more appropriate/varied transports. This has already been illustrated with SOAP-over-SMTP bindings, SOAP-over-XMPP, etc. <BR/><BR/>This is only one of the benefits of having headers within a SOAP message; there are many others (related to multiple parties in a "filter chain" each operating on a single SOAP message independently, intelligent message routing, security/policy/signing operations, etc.)<BR/><BR/>That said, the benefits of the SOAP specification don't really shine through unless you're performing relatively complex operations that involve multiple parties, cryptographic signing, routing, etc. Otherwise, SOAP may be seen as somewhat "heavy" for simple operations. SOAP/WS-* seems comparable to a swiss-army-knife; quite capable of almost anything you need, but carrying with it a certain amount of complexity and overhead.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8655567.post-1144068397840472692006-04-03T05:46:00.000-07:002006-04-03T05:46:00.000-07:00It should work like IP sockets: the application ju...It should work like IP sockets: the application just sends the data. Whee! I don't have to pack connection information into every struct that I send; once the connection is established and configured, it just looks like another stream.Anonymousnoreply@blogger.com