-
Tim doesn’t deserve this. His vision for the Web was far richer than what was deployed from 1991 to 2004. However, the W3C should be taking far more flack for poo-pooing Javascript’s importance.
-
Only 7% of SOA projects exceeded expectations. Main reason? “introduced more complexity into IT system”. No shit, Sherlock!
-
“Laugh and the world laughs with you, get killed by a benign piece of seafood and the world laughs too apparently” 8-)
-
“The fact is the most successful web services – since the beginnings of the web – were social software applications”
-
Nice pic, Stefan 8-)
-
“So who really cares that SOAP is able to be bound to MQ or IIOP or SMTP, today?”
Jorgen tries to convince us that Web 2.0 Needs WS-*. But he’s going to have do a lot better than arguments like this;
And, as if to underscore why I don’t see the REST / POX / AJAX “religion” achieving too much traction among enterprises, try explaining the phrase “The Web is All About Relinquishing Control” to any corporate security manager!
Well, if Jorgen had read what Alex was saying about relinquishing control, he might not think that such an insurmountable task;
This is possible because no one owns the web, and consequently no one can control it. The web is everyone’s property, and everyone is welcome to join in. It’s the world of sharing. The need for control has been relinquished, and it is left to the participants to sort their discrepancies out. The web as a medium and as a technology is not going to offer any assistance in that regard.
In other words, relinquishing control is largely about adopting public standards in lieu of pursuing proprietary interests, in particular the public Web standards that make inter-agency document-oriented integration (relatively) simple to achieve. If you are responsible for securing an Intranet, it should be your first and primary consideration to trust messages which are based on publicly vetted agreements, like most Web messages, and similarly, to distrust those messages whose complete semantics are not publicly vetted, like most SOAP messages.
-
Good post about of some of the practical issues of using caching, conneg, etc..
-
“the ‘To’ is sent as the HTTP Request-Uri” Yeah! “and the ‘Action’ is sent out as […] SOAP-Action” Boo! Action should be the HTTP Request-method (via Nick Gall)
-
Voice recognition problems in a public demo from Microsoft. ROTFL!
-
“I don’t understand why our expectations for music technology are so low that we accept MP3 as an audio equivalent for HTML”
-
“The Evans Data survey found a 37% increase in respondents implementing or considering REST, with one out of four surveyed saying that they are considering REST-Based Web Services as a simpler alternative to SOAP-based services.”
-
SOAPHttpRequest?! *groan*
-
… and shows a lack of understanding of REST and Web style services. Sounds like they could do with another co-CTO (Tim?) 8-)
-
“I suggest they roll some heads and figure out a real product strategy” Heh. Who couldn’t see that one coming? If I were them, I’d be be giving AOL a call.
-
“The biggest threat to Google isn’t that someone else will implement the same Calendar API as Google, it’s that someone will make web pages uncrawlable through proprietary extensions to HTML or HTTP”
-
No SOAP support. Not even a mention, AFAICT.
I was checking out the latest Atom Publishing Protocol draft today. It’s come a long way, and it’s surprisingly brief – thank goodness for that. I couldn’t help but feel a sense of regret though; SOAP could have been Atom.