All they mean is that you can have X instances
servicing potentially Y web clients, where Y>X.
That is to say that all requests are guaranteed
to not occur simultaneously, so they can 'share'
instances, and greatly cut down on system overhead.
Also, just because you are using stateless beans,
you can still store state in HttpSession and
connect to entity beans using said state. You're
just cutting down on session bean overhead (no
need to maintain so many session bean instances).
-David
-----Original Message-----
From: A mailing list for Enterprise JavaBeans development
[mailto:[EMAIL PROTECTED]]On Behalf Of Dave Ford
Sent: Tuesday, April 18, 2000 4:11 AM
To: [EMAIL PROTECTED]
Subject: Pooling Stateless Session Beans
I just read an article Java Developers Journal about stateless session ejbs.
It said one of the benefits of stateless ejbs is that they can be more
easily pooled. This may be a dumb question, but what is the point of pooling
a stateless bean? What exactly is getting pooled, if there is no state?
Isn't a stateless bean just a bunch of functions?
Dave
===========================================================================
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".
===========================================================================
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".
