On Fri, 31 Jan 2003 16:26, Berin Loritsch wrote:
> Strictly speaking, a stateless component is one that
> does not maintain information between method calls (AKA state).
I disagree. A stateless component is one that does not maintain *** client
specific *** information between method calls. If the service maintains state
that is shared between all clients then it is not stateless using that
terminology.
Using your example;
> One example of a state-ful component would be this:
>
> Store myStore = (Store) m_manager.lookup(Store.ROLE);
>
> myStore.save("mydoc", mydocument);
>
> //..... several invokations later .....
>
> mydocument = myStore.load("mydoc");
If the document is accessible by multiple clients then the above could still
be a stateless component. However in that case there is presumably no
guarentee that the document retrieved is the same one put in.
--
Cheers,
Peter Donald
*------------------------------------------------------*
| An expert is someone who knows everything about the |
| topic except for its place in the world. |
*------------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
