Return-Path: Delivered-To: apmail-ws-axis-c-user-archive@www.apache.org Received: (qmail 30423 invoked from network); 23 Jun 2008 05:00:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Jun 2008 05:00:55 -0000 Received: (qmail 41811 invoked by uid 500); 23 Jun 2008 05:00:57 -0000 Delivered-To: apmail-ws-axis-c-user-archive@ws.apache.org Received: (qmail 41792 invoked by uid 500); 23 Jun 2008 05:00:56 -0000 Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C User List" Reply-To: "Apache AXIS C User List" Delivered-To: mailing list axis-c-user@ws.apache.org Received: (qmail 41781 invoked by uid 99); 23 Jun 2008 05:00:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Jun 2008 22:00:56 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of shobhaac@lge.com designates 156.147.1.113 as permitted sender) Received: from [156.147.1.113] (HELO LGEMRELSE3Q.lge.com) (156.147.1.113) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Jun 2008 05:00:03 +0000 X-AuditID: 9c930171-abe97bb0000014f6-2a-485f2de2ee49 Received: from sishobhac (unknown [156.147.140.122]) by LGEMRELSE3Q.lge.com (Symantec Mail Security) with ESMTP id 30101558006 for ; Mon, 23 Jun 2008 14:00:18 +0900 (KST) From: "Shobha AC" To: "'Apache AXIS C User List'" References: <004701c8d360$95631940$190218ac@LGE.NET> <005f01c8d394$a2731250$190218ac@LGE.NET> Subject: RE: AXIS2c Handling the multiple requests. Date: Mon, 23 Jun 2008 10:30:17 +0530 Message-ID: <000001c8d4ee$08630070$170218ac@LGE.NET> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C8D51C.221B3C70" X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcjTx1DxhUQUxw3ISnqETy8hmlPSYQBJnd7A In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 X-Brightmail-Tracker: AAAAAA== X-Virus-Checked: Checked by ClamAV on apache.org ------=_NextPart_000_0001_01C8D51C.221B3C70 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, The URL http://www.developer.com/java/web/article.php/3620661 talks about the AXIS2 talks about session management support. Is this support available for Axis2/C or only for Axis2/JAVA Regards, Shobha _____ From: Supun Kamburugamuva [mailto:supun06@gmail.com] Sent: Saturday, June 21, 2008 7:50 PM To: Apache AXIS C User List Subject: Re: AXIS2c Handling the multiple requests. 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 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:supun06@gmail.com] 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 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 ------=_NextPart_000_0001_01C8D51C.221B3C70 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

The URL http://www.developer.com/java/web/article.php/3620661= talks about the AXIS2 talks about session management support. Is = this support available for Axis2/C or only for = Axis2/JAVA

 

 

Regards,

   = Shobha

 

 

From: Supun Kamburugamuva [mailto:supun06@gmail.com]
Sent: Saturday, June 21, = 2008 7:50 PM
To: Apache AXIS C User List
Subject: Re: AXIS2c = Handling the multiple requests.

 

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 <shobhaac@lge.com> = wrote:

Dear All,

         &= nbsp;  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:supun06@gmail.com]
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 <shobhaac@lge.com> = wrote:

Dear All,

    &nbs= p;       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,<= /o:p>

   Shobha

 

 

 

------=_NextPart_000_0001_01C8D51C.221B3C70--