At 08:48 PM 5/1/01 -0400, you wrote:
>On 2001.05.01, Tim Darling <[EMAIL PROTECTED]> wrote:
> > Further Enterprise Java Beans make websites that are
> > much faster because a DB call isn't made every time a user hits a
> > page. DB calls are 1,000 - 10,000 times slower than a call to a java bean
> > which is acting as an abstraction of the database.
>
>I can implement the equivalent of Java beans using two or three
>procs that act as wrappers around an nsv_* interface, all in
>Tcl and AOLserver API.
I'm with both Tim and Dossy here. There's a bit market for EJBs and
there's a lot that can be done in AOLserver itself.
I am curious: how do EJB's handle the ACID test? Is the performance
penalty a reasonable cost for those portions of your project that have ACID
requirements? Is the EJB/DB architecture more akin to a AOLserver as
application server/DB solution than the typical AOLserver as web server/DB
solution described so well in WTR? If so, does what can we learn/steal
from EJBs to make the AOLserver environment more productive, more
efficient, more powerful, or just more compatible?
Jerry
=====================================================
Jerry Asher [EMAIL PROTECTED]
1678 Shattuck Avenue Suite 161 Tel: (510) 549-2980
Berkeley, CA 94709 Fax: (877) 311-8688
