I agree Dan.
Bill
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of danch
> (Dan Christopherson)
> Sent: Wednesday, June 06, 2001 12:37 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] Avoiding Locks for READ-ONLY Beans
>
>
> It may well be usefull, but does this behavior belong in the normal
> EntityInstanceInterceptor? Why not just implement an non-blocking
> variant of EntityInstanceInterceptor, and reconfigure your stack in
> jboss.xml?
>
> K.V. Vinay Menon wrote:
>
> > OK!
> > I know that it is kind of controversial and that its spec
> violation and
> > stuff but why can't we have multi threaded beans for read-only
> cases? Why
> > should we be bothered about transactions? We don't lock the database for
> > selects do we? Non-purists who face real world performance
> issues - please
> > let me know if these is complete rubbish or is something that
> 'could' prove
> > useful...... unless someone voluteers to write the code for
> multiple bean
> > instances per home handle!
> >
> >
> > Vinay
>
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
