- From: Harald Fuchs <hf0722x@protecting.net>
- Date: 28 Oct 2004 14:56:15 +0200
- To: www-ws@w3.org
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 13:04:00 UTC