Hi Rajith pls see my in-line comments
Rajith Attapattu wrote: > Hi All, > > I have a question on the usability of the current scoping mechanism. > > As I understand the current impl has the following scopes when we > deply an application > > Application scope > Soap Session scope > Http Transport session scope > Request scope > yes we do > But I think they can be collapsed into 2 simple categories > > Stateful services and Stateless services. > Stateless = (Application and Request scopes) ohhh , I dont think if some one deploy a service in application scope it wont be a stateless service , it has state and which will be equal to application life cycle. In simple word if some one deploy a service in application scope , then there will only one instance of the service impl class life time of the system. So I can not agree with that services which are in application scope are stateless. > Statefull = (Soap session scope and Http Transport session scope) > > So I am wondering do we really need to have this distinction. Can we > not just simply denote wether the service is stateful or stateless. > Please correct me if I am wrong , Axis1 has the same terminology , and SOAP session is totally different from HTTP transport session. SOAP session is transport independent if client send the required SOAPHeadere parameter then we are happy to support SOAP session management.And transport session management happen using cookies. > With the new session mgt impl we can simply categorise services as > stateful and stateless. I think that is not enough I think we have to have multiple scope as well. > > What do you guys think?? > > Regards, > > Rajith -- Thanks, Deepal ................................................................ ~Future is Open~
