dan benanav wrote:
>
> I know this has been discussed somewhat in this newgroup but I haven't
> seen any real conclusion on what I am going to suggest here.
>
> It seems to me that stateless beans can be a good choice for caching
> database data under certain circumstances. One great thing about a
> stateless bean is that they provide automatic failover in a clustered
> environment. Also stateless beans are not passivated. Here are the
> conditions under which I think stateless beans can be used for caching.
>
> ...
>
> What do you think? Am I missing something here?
It seems perfectly workable to me, given the stated conditions.
> Sidebar: Stateless Session Beans and singletons.
> It seems to me that if you can specify that at most one stateless bean
> should be created then you could create a singleton. This relies on the
> fact that the container will serialize calls to the stateless bean.
<vendor>
Sybase EAServer allows you to specify a bean as being 'shared', in which case
we create only one instance per server process and serialize access to it if
that is requested. Our customers have been using this feature extensively for
the last 18 months and it works very well.
</vendor>
________________________________________________________________________________
Evan Ireland Sybase EAServer Engineering [EMAIL PROTECTED]
Wellington, New Zealand +64 4 934-5856
===========================================================================
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".
