> -----Original Message-----
> From: Imre Kifor [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, March 18, 1999 3:45 PM
> To: [EMAIL PROTECTED]
> Subject: Re: FW: (TO SUN: please clarify) Re: ejbCreate( ) -
> initialize
> instan ce variables
> The pools in EJB are not only for reducing the number of
> memory allocations.
> The ability to limit/adjust resource usage in a server is the
> secret behind
> the server's scalability. The various instance pools in an
> EJB server allow
> you to fine tune/balance the overall server for a specific
> configuration of
> resources. It is again a question of resource management.
> Without pools (or
> their functional equivalents) we cannot talk about scalable servers.
Couldn't the same thing be achieved via reference-counting? If you want to
have a maximum number of a certain EJB, just check to see if you've created
that many. If you have, fail the creation of new ones (or wait until the
number of EJBs falls below a certain threshold). When ejbRemove() is
invoked (or maybe ejbPassivate()), reduce the reference count.
Or am I missing something?
-jon
===========================================================================
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".
