Jon,
A stateless session bean does not have any state (thus stateless) because a
client is not guaranteed that two calls will reach the same instance of the
bean and therefore the same "state". However, you can have stateless session
beans that maintain state if it is not client-specific state that they hold.
If all your clients want quick access to the same ro data in the database
then a stateless session bean is one way to go.
>From: Jon Tirsen <[EMAIL PROTECTED]>
>Reply-To: A mailing list for Enterprise JavaBeans development
><[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: Caching of read-only DB contents in an EJB
>Date: Mon, 17 Jan 2000 20:06:49 +0100
>
>A stateless session does not have any state (duh!) which makes it pretty
>useless to handling any state at all (duh!) (such as a ro-data-cache).
>A session is not shared between clients which makes it pretty useless since
>the point of a cache is to optimize as many requests for data as possible.
>The entity seems to be the only way to implement caches in EJB (since they
>are shared by clients), but unfortunately they cannot be used either (at
>least not in portable manner). The entities state is for most containers I
>have tried flushed and read from the underlying datasource for each
>transaction. I guess some containers could implement some kind of
>intra-transaction cache of entities, but I haven't seen in the containers I
>have tried.
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
