netzooid

MyArch has a good article about achieving reliable semantics with your web service:

…we still might be able to use SOAP/HTTP if we make our service consumers a little smarter. Specifically, service consumers must be able to meet the following requirements: Consumers must be able to retry a Web service call in case of a failure due to a connectivity error… Consumers must be able to uniquely identify the data that they are sending to providers… Consumers must be able to handle certain application-specific errors (SOAP faults)…

There is also a good table of what you need to think about for simple CRUD operations (which are what most web services are) to achieve reilability.

This reminds me of the HTTP vs SOAP/WS-* discussion we were having at JavaZone. James Strachan suggested that we can easily achieve our own reliability with HTTP by creating a unique URL which the client POSTs to until they get a response code. While its not that transparent, it isn’t a huge pain either.

This entry was posted on Monday, October 30th, 2006 at 12:07 pm and is filed under Random.