Return-Path: Delivered-To: apmail-xml-axis-user-archive@xml.apache.org Received: (qmail 3374 invoked by uid 500); 28 Aug 2002 06:29:19 -0000 Mailing-List: contact axis-user-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-user@xml.apache.org Received: (qmail 3363 invoked from network); 28 Aug 2002 06:29:19 -0000 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Subject: RE: Iterator with Axis? X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Date: Wed, 28 Aug 2002 08:29:28 +0200 Message-ID: <89F2D7244FA78A48B8AD71BBC76E673486AFF3@bra-no-24-001.corp.bravida.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Iterator with Axis? Thread-Index: AcJN+6QWQYOQbiveQn21hkc8L0NPHwAX50ew From: To: X-OriginalArrivalTime: 28 Aug 2002 06:29:29.0045 (UTC) FILETIME=[43280850:01C24E5C] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Status: O X-Status: X-Keywords: The SOAP header that SimpleSessionHandler uses; is it a standard part of = SOAP, or is it propietary for Axis? E.g. will it work with a .NET = client? (I've heard that cookies will work with .NET, but I would like to be = independent of the transport method used (HTTP).) Regards, Eirik Wahl > -----Original Message----- > From: Les Gerads [mailto:tachophile@hotmail.com] > Sent: 27. august 2002 20:51 > To: axis-user@xml.apache.org > Subject: Re: Iterator with Axis? >=20 >=20 > I've built an iterator, but I used the session stuff Axis provides in > SimpleSessionHandler which uses the SOAP header to hold the=20 > session ids. I > know this will also work by turning on the HttpSession from the > MessageContext which uses the HTTP header (cookies). >=20 > I can't think of another way to do it on the server side=20 > without using some > type of session mechanism. >=20 > Les >=20 > ----- Original Message ----- > From: > To: > Sent: Tuesday, August 27, 2002 11:24 AM > Subject: Re: Iterator with Axis? >=20 >=20 > > I've done some consideration of how to deal with an > > Iterator, because of the stateless nature of Web Services > > it seems that you have to > > - consider the iterator as a client-side construct > > - build a web service that has an arbitrary state > > tracking mechanism (not a good idea) > > - build a server-side component with state (a servlet) to > > access the web service and avoid client-side bloat > > > > One thing you could do to help the Iterator scenario is > > to create a Web Service that guarantees order when > > accessing a set of primary keys, or allows you to acquire > > ordered keys without the data. > > > > Are there other insights out there? > > > > Paul > > > Has anyone tried to implement an Iterator with Axis? > > > Would this require the use of sessions so multiple calls=20 > using the same > > > iterator could be mapped to the same client? > > > > > > Eric H. Jung > > >=20