This post originated from an RSS feed registered with Java Buzz
by Chuck Hinson.
Original Post: SOAP Transport Independence
Feed Title: Chuck Hinson
Feed URL: http://chuckhinson.blogspot.com/atom.xml
Feed Description: Observations, questions and musings related to my life in the software industry.
More thoughts while reading...
I keep thinking about SOAP's use of HTTP as a transport protocol and the fact that SOAP is supposed to be transport independent so you can make use of existing protocols like SMTP or FTP or whatever. I gues my question at this point is why?
Why would I want to use SMTP instead of HTTP? What does that buy me? OK, so I dont need a web server to service requests - I can just float stuff through email. But now I need to write some new sort of server that can poll the service's 'inbox' and process the messages that it finds there. So not only do I still need some sort of server, but now I've got to write my own when I could have just used already existing and readily available web server software.
As to the question of why HTTP is the preferred protocol, I suppose I can see why that's the case. There's already lots of well tested HTTP client and server software out there, so its real easy to use. And just about everybody lets HTTP through the firewall. But isn't that really just a port number? I could run any protocol on port 80 and it would still make it through just about as many firewalls.
Well, back to reading. Maybe the answers will eventually become clear to me, but it just feels like the whole protocol independence thing and the use of HTTP has made things much more complicated than they need to be.
Previous Topic
