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

Re: Stateful services (was Web Service Description and stateful services)

From: Sergey Beryozkin <sberyozkin@zandar.com>
Date: Tue, 24 Jun 2003 17:46:16 +0100
Message-ID: <000901c33a70$21b16d50$1800a8c0@BERYOZKIN>
To: "Sergey Beryozkin" <sberyozkin@zandar.com>, "Savas Parastatidis" <Savas.Parastatidis@newcastle.ac.uk>, <www-ws-arch@w3.org>
Cc: "Paul Watson" <Paul.Watson@newcastle.ac.uk>, "Jim Webber" <jim.webber@arjuna.com>, "Thomas Rischbeck" <thomas.rischbeck@arjuna.com>, <arnaud.simon@arjuna.com>


I said :
> When I was saying that a service may want to expose different views of the
> same data for different customers (security context, for ex) or depending
> what stage the activity is. I thought it would be the second case. Let's
> assume a table in a database needs to be exposed. The service may want to
> return a different view of this table depending on some "application
> contained in a given request.
> So, this time :-) I think that there're indeed could be 3 different types
> state, but "3. State as in "data resource"" can turn into  "2. Application
> state"
What I meant was that in this case it's 2.Application State which tells a
service in what form that table's data need to be returned, or may be
whether this request for data should be refused because that customer has
read it to many times. This application state might include, for ex, URI
identifying the table, a counter of how many times a specific customer has
read this table, etc.

 Sergey Beryozkin
Received on Tuesday, 24 June 2003 12:46:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:41:07 UTC