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 > >>> > > > > >
