We have had in Domino for some time Web Services.
Now, after the release 8.5.3 one can install and deploy REST Services (http://extlib.openntf.org).
From my understanding the REST way is clearer and just feel right.
However, the Web Services are still for some reason here.
Now, as it looks like i’ll have to dive deeper into this topic, i’d like to set the question:
Does it have any reason to study and try to implement the Web Services or i’d rather start right away with the newest libraries?
(http://www.openntf.org/blogs/openntf.nsf/d6plinks/NHEF-8J994J )
Update.
Discovered the following Link/Duscussion SOAP or REST for Web Services?
Though it’s not Domino specific, but has a lot of good info. Now only some Domino-specific experience fails, which i’d be glad to see here…
SOAP beats REST by a large margin when it comes to system to system communication. Providing just one end point (the wsdl file) a reliable and verifiable grammar can be established: what can you do, what data is needed, what to expect in return. (Not sure if the latest we service spec extended the reliability to REST). REST based services on the other hand work by (manual) convention. You need to know the URL syntax, not just the location of the wsdl file and there is no relation to a schema other than doing a get and hoping the returned XML has one.
When it comes to browser system communication the picture is different. Here the lean operation of REST specifically when the payload is JSON beats the robust definition of SOAP any time. Just keep in mind you need to bar in for syntax and format. If you are on both ends – that’s easy to bargin then.
In conclusion: both REST and SOAP (actually both are called web services in the definition, it is only ‘colloquial’ to refer to SOAP when saying ‘web service’) have their ‘sweet spot’ use cases.