W3C home > Mailing lists > Public > www-ws@w3.org > November 2004

RE: Stateful Web Services...

From: Mullins, Chalon <Chalon.Mullins@schwab.com>
Date: Thu, 4 Nov 2004 08:24:49 -0800
Message-ID: <72796EB188CDD411A7BF0002A52CAC161C60A5A9@n1026smx.nt.schwab.com>
To: "'Geoff Arnold'" <Geoff.Arnold@Sun.COM>
Cc: www-ws@w3.org

Thanks, Geoff

But I don't think I am looking for the one true way.  I am only looking for

I absolutely agree about building on real world experience -- which is the
path being followed by GGF and Globus.

Chalon Mullins
Technical Director, Infrastructure Strategy and Architecture
Charles Schwab & Co., Inc.
101 Montgomery St
San Francisco, CA 94104
phone:  (415) 667-1117

-----Original Message-----
From: Geoff Arnold [mailto:Geoff.Arnold@Sun.COM] 
Sent: Thursday, November 04, 2004 8:21 AM
To: Mullins, Chalon
Cc: www-ws@w3.org
Subject: Re: Stateful Web Services...

On Nov 4, 2004, at 10:51 AM, Mullins, Chalon wrote:
> But -- we a lot of this happens because there is no standard way of
> maintaining a reference to the state between client and server.

If you are waiting for The One True Way, then I recommend that you "get 
used to disappointment" (cf. The Princess Bride). If you look at the 
collection of arguments that I gave for the distributed file access 
case, it should be clear that different use cases and workloads are 
going to lead to different solutions. In fact (irony alert) the latest 
versions of NFS introduce de facto stateful sessions. And that's OK.

Of course we want to identify common patterns and refactor to make them 
reusable. (I'd prefer to do this on the basis of actual, real-world 
experience rather than trying to dictate standards ahead of time, but I 
guess that's a lost cause.) But the bottom line is that there will be 
multiple models, multiple standards. Silver bullets and Procrustean 
beds lead to bad engineering.....
Received on Thursday, 4 November 2004 16:25:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:37:11 UTC