Hi Andrew!
Sessions are easy if you're using Axis on both sides - if not you have to make sure that your non-Axis client can send the right cookies/SOAP headers to use them. Then you set your service to be session-enabled: <service name="whatever" provider="java:RPC"> <parameter name="scope" value="session"/> ... </service> The other issue, asynchronous callbacks, is more interesting, but isn't something we support yet. You'd essentially need the abiliity to have Axis spawn off worker threads to handle asynchronous or process-based backends. Doable, but not for this release. --Glen > -----Original Message----- > From: Andrew Vardeman [mailto:[EMAIL PROTECTED]] > Sent: Friday, April 19, 2002 2:45 PM > To: [EMAIL PROTECTED] > Subject: how to implement sessions, persistent objects, etc. ? > > > Hi folks. > > My supervisor and I are hoping to use SOAP for communications > between a > handheld data collection instrument and the server where the data are > stored. For this we need a dialogue between the handheld and > the server > that will last for more than one request/response. If I > understand Axis > properly, each request is an island. How do I persist > session data? Or, > suppose I want the server to send two messages for every one > sent by the > client. Or, say I want to fire off an arbitrary number of > status messages > as I process the client's request. Is there any way (other > than writing a > separate program and having Axis communicate with it, which > seems to defeat > the whole purpose of Axis) to keep a process running that is > specific to > one client's session? Is it possible for the server to send > "responses" > without the associated requests? > > Does that make any sense? > > Andrew > >
