Hm. Look at HTTP sessions: they are typically related to a server, not a particular URL. I can log in to a site, and it can remember my name, my shopping cart, etc, across a whole slew of different URLs. I think it's the same with Web Services.

Of course, one can design this any way one wants. To continue the HTTP analogy, I could have a CGI script at a single URL which sets its own "session" cookie, and I can also let the servlet engine handle sessions with its webapp-wide cookie. This would be like the difference between sessions "under" the service for Axis, and sessions "above" the service. Maybe we should support both models? I think we need some use-cases in order to fully understand what we want from the idea of "sessions" before we make these decisions.

+1 about making sure performance is paramount. I think we've got the right idea with respect to flexibility and architectural elegance, we just need to make sure we can build it to work really well.

--G

----- Original Message ----- From: "Sanjiva Weerawarana" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Sunday, April 17, 2005 7:30 PM
Subject: Re: Fw: [Axis2] Purpose Deployment changes



ARGH .. YAGNI???

Of course something like a BPEL impl does not need to keep state
at that level, but for a single service, IMO it'll be far less
confusing if we say that session = "usage of a service". That's
consistent with the common usage of the term "session" and in
any case easier for people to understand.

If you would like to build a higher level thing we could consider
it but I definitely don't want to mix that with session. The
higher level thing is exactly like a BPEL process context right?
In that case my intuition is that it belongs outside the SOAP
engine, but I could be convinced otherwise.

The key for us will be to make sure that we don't slow everything
down with all this elegance. I think we can, we just need to be
ultra careful how its implemented.

Sanjiva.

----- Original Message ----- From: "Glen Daniels" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, April 15, 2005 5:52 PM
Subject: Re: Fw: [Axis2] Purpose Deployment changes



Hi Sanjiva!

No, session is "more global" than service - can't a session include
calls to multiple services (it can in Axis 1...)?

--G

Sanjiva Weerawarana wrote:
> Hi - not sure whether this went out; mail trouble. Sorry if its dup.
>
> Sanjiva.
>
> ----- Original Message ----- > From: "Sanjiva Weerawarana" <[EMAIL PROTECTED]>
> To: <[email protected]>
> Sent: Friday, April 08, 2005 12:23 PM
> Subject: Re: [Axis2] Purpose Deployment changes
>
>
>
>>Wrong order? Engine -> Service -> Session -> MEP -> Message ??
>>
>>Sanjiva.
>>
>>----- Original Message ----- >>From: "Glen Daniels" <[EMAIL PROTECTED]>
>>To: <[email protected]>
>>Sent: Thursday, April 07, 2005 7:46 PM
>>Subject: Re: [Axis2] Purpose Deployment changes
>>
>>
>>
>>>Dammit, missed one. :)
>>>
>>>
>>>>EngineContext ->
>>>>SessionContext ->
>>>
>>>ServiceContext ->
>>>
>>>>MEPContext (OperationContext) ->
>>>>MessageContext
>>>
>>>--Glen
>>>
>
>




Reply via email to