Certification ceases to make any business sense when performance sucks! The
customer is not bothered if you are running a J-2-E-E compliant / certified
app server. They are not even bothered if you use Java or COBOL as long as
they get what they want - a good user experience.At some point we have to
come out of shells of java purism and get some business sense into things.
Vinay
----- Original Message -----
From: "Jay Walters" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 06, 2001 4:55 PM
Subject: RE: [JBoss-dev] Avoiding Locks for READ-ONLY Beans
> I suppose it would get us out of the problem of being certified as J2EE
> compliant as well...
>
> -----Original Message-----
> From: K.V. Vinay Menon [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, June 06, 2001 11:46 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] Avoiding Locks for READ-ONLY Beans
>
>
> 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!
>
> <snip/>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
