On Mon, Dec 13, 2004 at 08:50:18AM -1000, Seth Ladd wrote: : >Another alternative would be to externalize the service itself onto a : >separate server, so you don't need to worry about shutting it down at : >all ;) : : Well, that's kind of what we do now. We expose the service via Hessian, : so that all webapps can access it (and avoid classloading issues of : implementation classes). I was hoping to avoid the overhead and expose : as regular classes via JNDI.
You have a tradeoff here: "overhead" vs "scalability/maintainability." I'm a big fan of the latter, especially given that you may have trouble getting your singleton to exist on multiple machines when your app grows. ;) -QM -- software -- http://www.brandxdev.net tech news -- http://www.RoarNetworX.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
