RE: Infinite Loops and webservices

Nice idea, but web services don't normally maintain a transaction id, so how
would you know whether the service has already been executed within a
specific transaction?

Anne

> -----Original Message-----
> From: www-ws-arch-request@w3.org [mailto:www-ws-arch-request@w3.org]On
> Behalf Of Fraser David
> Sent: Friday, April 19, 2002 8:30 AM
> To: www-ws-arch@w3.org
> Subject: Re: Infinite Loops and webservices
>
>
> A possible solution:
> Implement a stack-trace-like mechanism. Each service can check to
> see if it
> had already been executed. If so it could generate a soap fault. The next
> issue would then be one of trust. How can my webservice know that one has
> not tampered with the stack-trace?
> D.
>
> _________________________________________________________________
> MSN Photos is the easiest way to share and print your photos:
> http://photos.msn.com/support/worldwide.aspx
>