-
I knew I recognized crummy.com (home of Leonard Richardson of recent REST book fame) from somewhere! I used BeautifulSoup for a project a couple of years ago.
-
New AC outfitting for international executive-first.
-
“In short, if SOAP is only useful when used in conjunction with the advanced WS framework, then, for the time being at least, SOAP isn’t useful at all” Ding! Subscribed. P.S. Pete – one word to respond to your last paragraph; Atom.
I like how news of Sam and Leonard’s REST book is kicking off a new REST/SOAP thread. This time though, it seems the tables are turned and it’s the Web services proponents who are having to defend their preferred architectural style, rather than other way around. It’s about freakin’ time! I’m kinda tuckered 8-O
Sanjiva chimes in, in response to Sam’s probing questions;
ARGH. I wish people will stop saying flatly incorrect things about a SOAP message: it does NOT contain the method name. That’s just a way of interpreting SOAP messages […] SOAP is just carrying some XML and in some cases people may want to interpret the XML as a representation of a procedure call/response. However, that’s a choice of interpretation for users and two parties of a communication may interpret it differently and still interoperate.
Oh my.
Every message has a “method”; a symbol which is defined to have a certain meaning understood by sender and recipient so that the sender understands what it’s asking be done, and the recipient knows what it’s being asked to do. A recipient which doesn’t understand what is being asked of it cannot process the message for hopefully obvious reasons.
What Sanjiva’s talking about there is ambiguity as a feature of Web services; that some recipients will interpret a message to mean one thing, while others another. Note that this is very different than what the recipients actually do in response to the message; that can and should, obviously, vary. But varying interpretations of the meaning of the message? Absurd.
-
Eric provides some more info on the upcoming W3C “Web of Services for the Enterprise” workshop. I hope to attend.
-
Wow. What a beautiful, inspiring story about one man’s (Scott Adams) principled design of a (possible) cure to his lost voice.
-
Message to a certain TAG member and WS-Transfer editor; it’s time to pick sides, my friend.
-
Go Ladies!
-
Fibre to Toronto and Montreal, but no Ottawa! Gah!
-
“Ashwin walked us through the SOA Architectural Big rules. I made notes, crossing out the errors and replacing them with the relevant REST principles.” A good read.
-
Heh, he said “MIME Typen”. I hope I’m not offending anyone by finding that cute 8-)
-
Heh, I love it; SOA as Beta 8-) P.S. Jeff, the VHS version came out 15 years ago, not 5. 5 years ago somebody tried to put video on 8-track 8-)
-
“Can the Web fulfill industry and business requirements?” Pretty much, yah.
-
“Also, there is no logout button. I plan to take care of both problems for new schemes in Mozilla.” God bless you, Rob Sayre.
-
Not just the usual “Cool URI” suggestions…
-
Why REST kicks SOA ass in one word.
-
Doh, it should have been on the Web all along!
-
Thanks, Paul.
-
“The question is, do they really get it?” I’d love to be wrong, but I suspect not.
-
It scares me to think that the dweeb I knew at Nortel’s Computing Technology Labs – whose claim to fame at the time was an “agent system built atop HTTP” – could have been a billionaire.
-
Ay carumba. How hard is it to just say “WS-Transfer is a piece of crap”? I doubt anybody would be offended anymore since, AFAIK, nobody’s implementing it.
-
So if “2.0” is the new big thing, and it takes Microsoft three versions to get it right, well , erm …. 8-)
-
Coach fails the “404; bug or feature?” test.
-
“The Team also plans to ask the Technical Architecture Group (TAG) to investigate the impact of this technology on the architecture of the Web” Time for some ass kicking!! 8-)
-
“And with more and more people suffering from WS-* protocol fatigue, that is very very welcome in my opinion.”
-
My friend and business partner, John Criswick, will be Canada’s first space tourist.
-
Of course it is.
-
What a strange article. Some great insight in places, but also some whoppers. In the end the conclusion is the predictable “SOA for complex apps, REST for simple ones”.
-
“But what was unexpected to me is that the act of geotagging, rather than the chore I expected, is rewarding in and of itself”
-
“Case in point: The Web services alphabet soup of WSDL, SOAP and UDDI. These standards enable unprecedented interoperability among critical business applications.” *groan*