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

RE: Web Service Description and stateful services

From: Cutler, Roger (RogerCutler) <RogerCutler@chevrontexaco.com>
Date: Tue, 20 May 2003 08:50:43 -0500
Message-ID: <7FCB5A9F010AAE419A79A54B44F3718E026EF734@bocnte2k3.boc.chevrontexaco.net>
To: "David Orchard" <dorchard@bea.com>, "Christopher B Ferris" <chrisfer@us.ibm.com>, "Savas Parastatidis" <Savas.Parastatidis@newcastle.ac.uk>
cc: www-ws-arch@w3.org

I'd still like to hear specifically what these people are doing and, if
possible, what motivated them to put it in this place.

-----Original Message-----
From: David Orchard [mailto:dorchard@bea.com] 
Sent: Tuesday, May 20, 2003 8:23 AM
To: 'Christopher B Ferris'; 'Savas Parastatidis'
Cc: www-ws-arch@w3.org
Subject: RE: Web Service Description and stateful services



I think that Savas might be talking about something a little different
than an implementation detail.  There is the question of how do
endpoints exchange state information, and any standardization of that.
There are some different types of standardization, like explicit
elements/attributes, or of an extensible container that can contain app
specific elements/attributes.

Cheers,
Dave

> -----Original Message-----
> From: www-ws-arch-request@w3.org [mailto:www-ws-arch-request@w3.org]On
> Behalf Of Christopher B Ferris
> Sent: Tuesday, May 20, 2003 2:03 PM
> To: Savas Parastatidis
> Cc: www-ws-arch@w3.org; www-ws-arch-request@w3.org
> Subject: RE: Web Service Description and stateful services
>
>
>
> +1
>
> Christopher Ferris
> Architect, Emerging e-business Industry Architecture
> email: chrisfer@us.ibm.com
> phone: +1 508 234 3624
>
> Savas Parastatidis wrote on 05/20/2003 07:57:37 AM:
>
> >
> > >
> > > But whether WSD or WSCHOR eventually looks into this, I *do* think
> > that we
> > > need to have concepts/relationships that describe how a
> Web service
> > > maintains its state.  This is obviously tied up with the
> more abstract
> > > discussions we've had over the role of "statelessness" in the Web 
> > > architecture.
> > >
> >
> > Surely, the way a Web service maintains its state must be an 
> > implementation detail. How do we refer to/address that
> state and whether
> > there is value in providing a standard way for 
> > creating/modifying/accessing it should be the topic of
> discussion, but
> > in the appropriate WGs.
> >
> > .savas.
> >
> >
>
>
Received on Tuesday, 20 May 2003 09:51:18 GMT

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