Jon Brisbin wrote: > I'm worried that having only > one object to handle any and all requests will be limiting. > Is this a problem?
In principle, as long as your object doesn't hold any locks (i.e. doesn't use synchronization), having one object handling lots of requests is a good thing for scalability. This is the rationale behind stateless session beans in EJB. Problems for scalability are: * Holding locks. If your object is stateless, it doesn't need to hold locks. * Allocating memory frequently. Memory allocation is slow. If you have only one object handling all requests, you never need to allocate a new one. * Allocating lots of memory. If you only need one object, you conserve memory. That said, I don't know enough about the JMX code in JBoss to say whether there are other issues to consider. Ben ________________________________________________________________________ This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ________________________________________________________________________ ------------------------------------------------------- Sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source & Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
