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

Re: Stateful Web Services...

From: Francesco Furfari <francesco.furfari@isti.cnr.it>
Date: Thu, 28 Oct 2004 16:43:17 +0200
To: hf0722x@protecting.net
Cc: www-ws@w3.org
Message-id: <41810585.7070908@isti.cnr.it>

I'm just starting to study the work around grid services. Ian Foster et 
Al in
"Modeling Stateful Resources with Web Services"  says :
"... it is desiderable to represent such relationships between Web 
Services and state explicitily and in a standard manner,..."
If I remember well in Axis to activate the session mechanism you have to 
use SESSION_MAINTAIN_PROPERTY.
Changing WS engine, with  JWSDP (1.3) for instance, you have to manage 
the session by yourself ...
So,  in my opinion, web services are simply managed software that expose 
service interfaces in a standard machine-processable format
and we could  improve interoperability if the standardization process 
concerns the state rapresentation too.

ciao
francesco



Harald Fuchs wrote:

>In article <07b501c4bc28$d7c37080$2203a8c0@critical.pt>,
>Cristóvão Bento <cbento@criticalsoftware.com> writes:
>
>  
>
>>Although there is one last thing that is confusing me. A Web Service
>>life is controled by a Web Server like for example Tomcat. When a
>>request arrives, the class that implements the request is
>>dynamically loaded and the request is executed. When the request
>>ends the class is deallocated. This means this class cannot maintain
>>its internal state. Any kind of data that was kept by it is garbage
>>collected.
>>    
>>
>
>Nobody sys that you need something like Tomcat to implement a web
>service.  A small Perl script, started by inetd, would do likewise.
>
>If you want to maintain state, you need two things:
>1. A stable "backend" where you can store state, independent of the
>   lifetime of the code implementing the web service
>2. A way to identify the requestor for whom you want to maintain
>   state, something like a cookie.
>
>
>
>
>  
>
Received on Thursday, 28 October 2004 14:50:21 GMT

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