Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 94101 invoked by uid 500); 26 Sep 2001 03:38:36 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 94092 invoked from network); 26 Sep 2001 03:38:36 -0000 Message-ID: <005001c14639$b4052200$6b00a8c0@ne.mediaone.net> From: "Glen Daniels" To: , "Axis Development $E-Mail$" References: <003c01c145ad$a4cb2500$ed23bad4@jezzz> Subject: Re: Hi + congrats + Contrib proposal Date: Tue, 25 Sep 2001 23:16:58 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_004D_01C14618.2C8ECCC0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. ------=_NextPart_000_004D_01C14618.2C8ECCC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Christoph! This is a great project - we'd been thinking of adding something along = these lines, but hadn't gotten around to it yet. Glad you're working on = it! I assume you've already looked at the session support built into Axis = via the getSession()/setSession() APIs in the MessageContext and the = SimpleSession implementation. So essentially your session-management = Handler just needs to keep track of a list of active sessions by ID, = generate new ones when appropriate (i.e. when the SOAP session header = isn't present, make a new session and send back a header containing the = new ID), and time old ones out. Does this sound about right to you? --Glen ----- Original Message -----=20 From: Christoph C. Cemper @ Cemper.com=20 To: Axis Development (E-Mail)=20 Sent: Tuesday, September 25, 2001 6:34 AM Subject: Hi + congrats + Contrib proposal Hi folks, after working with Apache SOAP i performed a switch to AXIS for the = handler-features! Congratulations, as far as I can judge it, AXIS really is a big step = from Apache Soap. I am currently working on a sample of a handler that performs = processing of the SOAPHeader for implementing a sort of session handling. Reason for that is, that the whole cookie-mechanism for session = handling is not supported by other platforms like MS.NET=20 Furthermore performing that meta-info-processing via the SOAPHeader = seems much better because of it's protocol transparency. Ok, what I can offer/contribute is that sample including - Java-Code - VB-Code for MS.SOAP Toolkit How would that contribution work? Who will review/checkin the code as = soon as it is ready? mfg / kind regards,=20 Christoph C. Cemper=20 email: mailto:Christoph@Cemper.com=20 www: http://Christoph.Cemper.com=20 =20 ------=_NextPart_000_004D_01C14618.2C8ECCC0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi Christoph!

This is a great project - we'd been = thinking of=20 adding something along these lines, but hadn't gotten around to it = yet. =20 Glad you're working on it!

I assume you've already looked at the = session=20 support built into Axis via the getSession()/setSession() APIs in the=20 MessageContext and the SimpleSession implementation. So = essentially your=20 session-management Handler just needs to keep track of a list of active = sessions=20 by ID, generate new ones when appropriate (i.e. when the SOAP session = header=20 isn't present, make a new session and send back a header containing the = new ID),=20 and time old ones out. Does this sound about right to = you?

--Glen

----- Original Message -----
From:=20 Christoph C.=20 Cemper @ Cemper.com
To: Axis Development (E-Mail) =

Sent: Tuesday, September 25, = 2001 6:34=20 AM

Subject: Hi + congrats + = Contrib=20 proposal

Hi=20 folks,

after working with=20 Apache SOAP i performed a switch to AXIS for the=20 handler-features!

Congratulations,=20 as far as I can judge it, AXIS really is a big step from Apache=20 Soap.

I am = currently=20 working on a sample of a handler that performs processing of the=20 SOAPHeader

for = implementing a=20 sort of session handling.

Reason for that=20 is, that the whole cookie-mechanism for session handling is not = supported by=20 other

platforms like=20 MS.NET

Furthermore=20 performing that meta-info-processing via the SOAPHeader seems much = better=20 because

of = it's protocol=20 transparency.

Ok, = what I can=20 offer/contribute is that sample including

-=20 Java-Code

- = VB-Code for=20 MS.SOAP Toolkit

How = would that=20 contribution work? Who will review/checkin the code as soon as it is=20 ready?

mfg / kind=20 regards,
Christoph C. = Cemper

email: mailto:Christoph@Cemper.com=20
=20 www: http://Christoph.Cemper.com=20

------=_NextPart_000_004D_01C14618.2C8ECCC0--