Hi, AFAIK there isn't a mechanism for session management in Axis2/C. I think this is a nice feature we should support. We'll let you know what our future plans for this.
Regards, Supun.. On Sat, Jun 21, 2008 at 4:47 AM, Shobha AC <[EMAIL PROTECTED]> wrote: > Dear All, > > Is there any mechanism for session management in AXIS2 > architecture? > > Like Eg: > > > > 1. Login Request > > If authenticated user then allow for next web service i.e > > 2. Set Static IP Address. > > > > > > Or for each request-response exchange there needs a session id to be > exchanged as part of WSDL calls. > > > > Regards, > > Shobha > ------------------------------ > > *From:* Supun Kamburugamuva [mailto:[EMAIL PROTECTED] > *Sent:* Saturday, June 21, 2008 12:28 PM > *To:* Apache AXIS C User List > *Subject:* Re: AXIS2c Handling the multiple requests. > > > > Hi, > > This is handled at the transport level. When a TCP connection (HTTP is the > application layer protocol) is stabilized between the server and the client > this get handled automatically. Also Axis2/C doesn't have any state > information about the clients that are connected to it. It gets a request > via a TCP (HTTP is the application layer protocol) and through that same > connection it sends the reply. > > Supun. > > On Fri, Jun 20, 2008 at 10:35 PM, Shobha AC <[EMAIL PROTECTED]> wrote: > > Dear All, > > Can anyone tell how the requests from different clients for the > same service api is handled? > > Like sending the respective response to the respective clients.. > > > > Regards, > > Shobha > > > > >
