According to Mark Baker most developers (85% vs 15%) will use the HTTP-based mechanisms for accessing the Amazon S3 service. This is because the “SOAP interface is comical”. I won’t try to support Amazon‘s design. That’s their job. I would like to make a comment from a developer’s point of view.
As much as I dislike WSDL because of its use of the ‘interface’ and ‘operation’ abstractions, it still represents a technology in the Web Services metadata space which doesn’t have a widely accepted and well supported equivalent in the HTTP-as-application-protocol world yet. I just tried WCF‘s WSDL-to-code generation utility against the Amazon S3 WSDL (“svcutil http://s3.amazonaws.com/doc/2006-03-01/AmazonS3.wsdl”) and voila, I have code to help me start. Granted, it gives me an object-oriented interface which I dislike rather than a message-oriented one but the point is that I used a declarative description of the service as a tool to bootstrap my interaction. Now, when we start using WS-Policy and messaging-behaviour descriptions like SSDL the sky is the limit 🙂
Don’t get me wrong, I am not arguing against the HTTP-based mechanisms. Obviously we need both. I just missed the blogosphere discussions 🙂
See "BrainExpanded - Introduction" for context on this post. Notes and links Over the years,…
This is the first post, in what I think is going to be a series,…
Back in February, I shared the results of some initial experimentation with a digital twin.…
I am embarking on a side project that involves memory and multimodal understanding for an…
I was in Toronto, Canada. I'm on the flight back home now. The trip was…