Web Things, by Mark Baker

As relayed by Nelson Minar, author of two of the Google APIs;

From my experience nothing interoperates well, even in the basic SOAP stack. rpc/encoded used to work OK, within its limitations but now that’s deprecated it’s not a realistic option for new services. So you’re stuck with document/literal where practice isn’t great.

And remember, this is just SOAP 1.1 a spec that is five years old, and which (apparently) requires clarification upon clarification… but still can’t seem to get it right.

Ouch. Even if you like the (presumed) architecture of Web services, this would seem reason enough to give pause and to motivate consideration of a Web based solution, no?

Update; based on some offline feedback, I should clarify that the problem Nelson talks about with the doc/lit encoding isn’t specific to Web services and could also be encountered in a Web based solution. But my intent here is just to throw cold water on the general concept of “SOAP = interoperability”, and to point out that the largest distributed application ever created by mankind – the Web – got that way because it truly embraced interop, and wasn’t just paying it lip service.

… has been posted.

In addition to my DevDay co-chairing duties, I’ll be part of a panel called – at least for now – “Web services considered harmful?” 8-). You’ll recognize all the participants, but I won’t name any yet since I’m not sure who’s confirmed. Rohit Khare will be moderating.

James writes;

If you’re in Boston and interested in meeting up, let me know!

I’ll be seeing far too much of Boston over the next three weeks. I’ll be there on the 17th and 18th (departing on the evening of the 18th), as well as 27th through March 2nd (departing afternoon of the 3rd). I’m currently only booked up on the evening of the 27th, though I expect that one of the other evenings that week will be booked up too.

Gee, I can’t remember how long it’s been since I last saw James.