Hi Kalle,
A web service doesn't always need state in order to interact with a legacy
program. The state can be stored in the legacy program, rather than the
actual web service. Web services also often use databases to store state
that must persist across multiple requests.
You may be interested in the WSRF Specifications:
http://www.globus.org/wsrf/
Here is their "Motivation" text:
---
Web services must often provide their users with the ability to access and
manipulate state, i.e., data values that persist across, and evolve as a
result of, Web service interactions. And while Web services successfully
implement applications that manage state today, we need to define
conventions for managing state so that applications discover, inspect, and
interact with stateful resources in standard and interoperable ways. The
WS-Resource Framework defines these conventions and does so within the
context of established Web services standards.
---
Cheers,
Tom
-----Original Message-----
From: Nice To Know [mailto:[EMAIL PROTECTED]
Sent: 22 December 2004 10:04
To: [EMAIL PROTECTED]
Subject: Web Service with state
Hi!
I'm building a web service that need a internal state. This is needed
because the web service will start a legacy program that takes input from a
prompt. This is my calls:
int threadId : runProg( String args )
void sendInput( threadId, String args)
String getResult( threadId)
Have read that web service has to be state-less. Why is that?
Unfortunately I have no choice here because I cant rewrite the legacy
application.
Thanks in advance
/Kalle
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
