Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (asf.osuosl.org: domain of davanum@gmail.com designates
 66.249.82.202 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=d8MeCT5tjjMz1Hd868YlYJJcCPcVe/IEcO2nNhT6EUtxLaVNcS8dyY7mZbhAKBzbLwoUius20W8HKNji4ZOHeckOgM8/87oryysABZ5lL+d0uVcKuVtwSRDAm3fPSmfNbHlUNJ0Bx4Y5J/8HJoKTZEALQ/tOpJpF4zggEUYYGpg=
Message-ID: <19e0530f0512300458m7b8fd1e6g5e8ed5dee9784c84@mail.gmail.com>
Date: Fri, 30 Dec 2005 07:58:17 -0500
From: Davanum Srinivas <davanum@gmail.com>
Reply-To: dims@apache.org
To: axis-dev@ws.apache.org
Subject: Re: [VOTE] [Axis2] Sessions on by default?
In-Reply-To: <1135942132.8593.9.camel@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <19e0530f0512260537y7e5a663apbbe17db89b568475@mail.gmail.com>
	 <43B09E32.30308@opensource.lk>
	 <f43ea5790512261816l46fab293yb985145f86dd2020@mail.gmail.com>
	 <559c463d0512262112r2b980041u17ac65f1271e75c0@mail.gmail.com>
	 <43B0FDA6.5090304@t-online.de>
	 <1135942132.8593.9.camel@localhost.localdomain>

Just noticed this....Sorry, the VOTE inluded both sides,

"A default server generated by WSDL2Java and a client generated by
WSDL2Java"

So it's not just the client.

thanks,
dims

On 12/30/05, Sanjiva Weerawarana <sanjiva@opensource.lk> wrote:
> On Tue, 2005-12-27 at 09:39 +0100, Werner Dittmann wrote:
> > [X] - Don't switch on sessions by default
> >
> > Well, I'm not an Axis developer, but makeing web services
> > "statefull" (session aware) by default is IMO not a good idea.
> > If some web services need "session" it should be done deliberatly
> > because the system must take care of the session data.
> >
> > Just think about scaleability (load sharing) of webservices on
> > different servers using IP load balancers. If a service
> > needs some state (session data) this state must be replicated
> > to all servers by some means, otherwise you can't perform
> > load sharing. Such a thing has to be designed, your overall
> > solution must be aware of it etc etc.
>
> Werner, you've got it all backwards .. the issue is on the client side,
> not on the server. On the server if the service is session scoped then
> you *have to* create service contexts and store them against the cookie
> ID until they time out. *None* of the points you made apply to the
> situation at hand!
>
> The question Dims asked is about what the default should be for clients.
> I disagree with the apparently popular choice of no sessions because if
> a service has multiple operations then in most cases the operations have
> some relationships between them. The question really amounts to asking
> how often do people have session scoped services vs. application scoped
> services. If they are application scoped then basically the cookie stuff
> makes no difference: either the service is totally stateless and it
> ignores all context or its truly stateful and remembers something from
> every request.
>
> IMO the natural behavior should be to maintain sessions by default.
> That's what even Apache SOAP did back many years ago.
>
> I was out of town for a few days so was not able to reply in a timely
> manner to convince more voters :(. Can we have a re-vote based on the
> information that Werner's explanation does not apply at all and at least
> 3 people voted based on that?
>
> Sanjiva.
>
>
>


--
Davanum Srinivas : http://wso2.com/blogs/