W3C home > Mailing lists > Public > www-ws-arch@w3.org > May 2003

RE: Web Service Description and stateful services

From: Jim Webber <jim.webber@arjuna.com>
Date: Tue, 20 May 2003 19:40:39 +0100
To: "'Assaf Arkin'" <arkin@intalio.com>, "'Savas Parastatidis'" <Savas.Parastatidis@newcastle.ac.uk>
Cc: <www-ws-arch@w3.org>
Message-ID: <000e01c31eff$5072cb20$0400000a@stan>

Absolutely right on the button I think. (Makes crash recovery a whole bunch
easier too.)

The service should always be able to "reconstruct" its internal state
machine that implements the business logic with the message that causes the
service invocation.

> IMO the Web service as a Web service - whatever that elusive 
> definition 
> is - should be stateless. But in a lot of cases there would 
> be a state 
> behind it and it would be accessed by referencing that state. 
> Think of 
> your trusty bank teller. He/she/it is stateless, you can go to any 
> teller that is available or use an ATM machine to access your 
> account. 
> But there's some state that you would always reference by giving an 
> account number before performing any transaction. And the notion of 
> providing an account information to carry out a transaction 
> is part of 
> the interface definition of all tellers.
Received on Tuesday, 20 May 2003 14:40:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:19 GMT