On Sat, 2008-06-21 at 17:17 +0530, Shobha AC wrote: > Dear All, > > > 1. Login Request > > If authenticated user then allow for next web service i.e
There are some authentication mechanisms which can be used with Axis2/C. see following, [1]http://ws.apache.org/axis2/c/docs/axis2c_manual.html#http_auth and, Rampart/C username token support [2]http://ws.apache.org/rampart/c/docs/configurations.html -Manjula. > > 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 > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
