I am almost convinced that if you create a web method to save an order and
you return the order number. If you call this method enough times you will
find that some orders did not get sent. The web method call will timeout.
At that point you can decide to re-send the orders. If you do, in some cases
you will have duplicate orders. If you do not use WS-RM you will need to
implement WS-R in your web method, by passing in a unique key and preventing
your web method from duplicating the order. If the client sends the same
order more than once you simply return the already assigned order number.
"Chris Fink" wrote:
I am not aware of anything that exists currently in any of the .NET
Frameworks or WSE3. Following is a link that I found
http://msdn.microsoft.com/webservice...mspecindex.asp
"John Grant" wrote:
http://www-128.ibm.com/developerwork...ry/ws-rmpaper/
When I make a web service call from the caller I want to know if the service
has executed or not.
"Chris Fink" wrote:
Please elaborate on your definition of reliable messaging.
>
"John Grant" wrote:
>
If I build a web services today with VS 2005 does it support reliable
messaging?
If I use WSE 3.0 will it support reliable messaging?
If I don’t have reliable messaging can I make a web method call that does
not reach the web service?
If so, what does the call do? Timeout, hang?
thanks
