How NOT to do RESTful Web Services

REST s'impose un peu partout, on commence donc a voir fleurir des gens qui rajoutent du REST a toute las sauces. Un article intéressant pour comprendre un peu que tout n'est pas REST...

Un autre article d'IBM explique ceci :

Does WSDL 2.0 enable REST?

The motivation of WSDL 2.0 HTTP binding is that it allows services to have both SOAP and HTTP bindings. The service implementation deals with processing application data, often represented as an XML element, and the service doesn't know whether that data came inside a SOAP envelope, HTTP GET, or HTTP POST. WSDL 2.0 HTTP binding enables you to expose a service as a resource to be invoked using HTTP methods. At the same time, you need to understand that HTTP binding doesn't enable you to implement a full REST style system. This is often debated by a lot of people, and it all depends on how much you believe in what REST can deliver.

Pour faire du REST il faut faire simple ce qui ne veut pas dire que REST soit simple et que les ws-* c'est plus riche. Si c'était le cas ils pourraient englober REST facilement !