I'm tired of reading posts blaming WSDL, WS-* specifications, requiring those behind it all to apologise and proclaiming REST is the only ever way to do it all. Common, lets stop it. I'm finding it both hilarious and ridiculous.
If you truly believe in REST then my advise is to teach and not to blame. Teach it the way the authors of the RESTful Web Services do it (though WSDL is not treated as a winner there too :-)).
And be realistic. I'm wondering what WSDL blamers will start saying when people will do RPC-style services with WADL. Blaming WSDL for allowing people to write RPC-based services is pointless. Teaching on how to concentrate on the data and to evolve these data has much more value.
Subscribe to:
Post Comments (Atom)
2 comments:
Is WADL seriously considered to go hand-in-hand with REST? I get the impression that it's just another miscreant of Sun's that will go the way of the entity bean.
WADL is considered by many people writing RESTful services be a better description language. Still, the code-generation is considered the evil thing at the same time by other people.
I reckon though, in the context of this entry, is that, irrespectively of which description language you use you can still end up writing an RPC service, which is what WSDL is blamed for allowing to do.
Post a Comment