Dan Christopherson cried: > If you're in an ISP/ASP environment where your control of the running > code is limited, I suppose I can see it, but it really pains me to see > people running one vm per application when the apps are developed > in-house.
I feel your pain. :) I got the impression that the original post was for an ISP environment, which is why the separate vm's make sense to me. But I agree that for a single organisation it can seem really stupid to have every app running in a different process. Especially when they most probably share many components. I think there comes a point where applications must be split into manageable groups, but only when there are so many that a single server cannot handle them all. > I'd feel a bit differently if the VMs were at least fork'ed > off of each other so that _some_ of the memeory would be shared. One of > the things application servers are supposed to do is help us share > resources - memory and process table entries being two of the more > fundamental resources. I expect that Java VM's will soon start using some kind of shared-memory system. Something like Web browsers use to track session cookies, graphics and the like. If they do not already have this functionality. At the very least, this would shave several seconds off the vm start time. - Matthew _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
