Chandra Seetharaman wrote: > On Mon, 2006-09-18 at 12:56 +0400, Pavel Emelianov wrote: > > <snip> > > >> The same for the limiting - either do not start new container, or >> recalculate limits to meet new requirements. You may not take care of >> guarantees as weel and create an overcommited configuration. >> >> And one more thing. We've asked it many times and I ask it again - >> please, show us the other way for providing guarantee rather than >> limiting or reserving. >> > > Why do we want the capability to be snipped at the infrastructure level. > Let the controller writers decide how they want to provide the > capability and the users to decide if they want to use the feature at a > price. >
That's what we proposed in the very beginning - to review an infrastructure with minimal functionality (limiting) and develop new features after the "core" is accepted. I'm glad that we've finaly made a bargain :) > >> ------------------------------------------------------------------------- >> Using Tomcat but need to do more? Need to support web services, security? >> Get stuff done quickly with pre-integrated technology to make your job easier >> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >> _______________________________________________ >> ckrm-tech mailing list >> https://lists.sourceforge.net/lists/listinfo/ckrm-tech >> ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
