On Mon, 24 Jun 2002, Glenn Nielsen wrote: > +1 to add a Tomcat specific performance testing/benchmark repository. > > Perhaps it would be best if it were in its own repository, > jakarta-tomcat-benchmark ? I will help as I have time.
I think we have 3 +1s and one -1 - maybe Remy can change his vote ? I don't thing j-t-benchmark is a good idea ( see later ), it should be in the same place with the tests ( and the total time to run the watchdog or product tests is a benchmark by itself ) > The latest Tomcat 5 proposal looks much better. I am still -1 for > starting the work until the JCP releases JSR 152 and JSR 154 for > public review. If you are talking about the implementation of the servlet/jsp part - I totally agree, it would be pretty hard to implement it without reading it first :-) The JSP2.0 PD seems to be out ( and much larger than the previous, it'll take few days to read it - I'm afraid we'll have a bloat fest..). Regarding the other enhancements to Coyote and other parts - I think we can start planning and discussing, that will take some time. Most of the work for 5.0 will actually be the same as work for 4.1 - so we are in effect working on it already. > There is one addition to the proposal I think we should discuss at > this time. That is the organization of the CVS repostories for > Tomcat. Yes, that's a big pain for me too. > The trend started a while ago was to break out common components into > their own repository. jakarta-tomcat-connectors and > jakarta-tomcat-jasper for example. > > Perhaps this would be the time to consider if there are better ways > to organize the code. The reorganization would have three goals: > > 1. Allow sharing of components between different versions of Tomcat > > 2. Reduce duplication and maintenance of code in multiple branches of > one CVS repository. > > 3. Make the code base in each repository more tightly focused on > what it does, thus making it easier for developers to find bugs > and submit patches. > > As an example, there are now at least 4 different versions of jasper > in various repositories. > > jakarta-tomcat-jasper/jasper34 > jakarta-tomcat-jasper/jasper2 > jakarta-tomcat/jasper > jakarta-tomcat-4.0/jasper > > Tomcat 5 would add a fifth. > > There are many other things that would be in common between Tomcat 4 > and Tomcat 5 which are not dependent on the Servlet or JSP version. > Moving these out of the core Tomcat CVS repositories would make life > easier. > > Thoughts? +1, but I don't like creating too many CVS repositories, and I don't think we should create too many big disruptions. What about a jakarta-tomcat-modules/ CVS repository, with a structure similar with commons or taglibs ? All new components will go there - and eventually we can migrate any old component that gets refactored and we make the code more modular. I think we should keep j-t-c and j-t-j, those are pretty big chunks. Eventually j-t-5.0 should only contain the servlet implementation, with no module, coyote will be in j-t-c - and all other modules in j-t-m. ( well, that's a quick proposal - I'm not very sure it is good ) Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
