Re: [VOTE] Apache Tomcat 5.0 Proposal

[costinm]

On Tue, 2 Jul 2002, Remy Maucherat wrote:

> After trying to address the concerns raised by the proposal draft, I 
> would like to call for a vote on it, now that the discussions have died 
> down.
> 
> 
> [X] +1 I support the proposal, and will help implement it
> [ ] +0 I support the proposal
> [ ] -0 I do not support the proposal
> [ ] -1 I am against the proposal being implemented, because:
> 
> 
> 
> 
> The vote will run for one full week until July 9th. Users and other 
> contributors may vote, but only committers have binding votes.

I won't read the mail for the rest of the week ( I'll be back next Mon ).

Costin


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: [VOTE] Apache Tomcat 5.0 Proposal

[GOMEZ Henri]

>
>[X] +1 I support the proposal, and will help implement it
>[ ] +0 I support the proposal
>[ ] -0 I do not support the proposal
>[ ] -1 I am against the proposal being implemented, because:
>

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: [VOTE] Apache Tomcat 5.0 Proposal

[Mladen Turk]

[X] +1 I support the proposal, and will help implement it
[ ] +0 I support the proposal
[ ] -0 I do not support the proposal
[ ] -1 I am against the proposal being implemented, because:





MT.


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: [VOTE] Apache Tomcat 5.0 Proposal

[Larry Isaacs]

> -Original Message-
> From: Remy Maucherat [mailto:[EMAIL PROTECTED]] 
> Sent: Tuesday, July 02, 2002 7:57 PM
> To: Tomcat Developers List
> Subject: [VOTE] Apache Tomcat 5.0 Proposal
> 
> 
> After trying to address the concerns raised by the proposal draft, I 
> would like to call for a vote on it, now that the discussions 
> have died 
> down.
> 
> 
> [x] +1 I support the proposal, and will help implement it
> [ ] +0 I support the proposal
> [ ] -0 I do not support the proposal
> [ ] -1 I am against the proposal being implemented, because:
> 
> 
> 
> 
> The vote will run for one full week until July 9th. Users and other 
> contributors may vote, but only committers have binding votes.
> 
> Remy
> 

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: [VOTE] Apache Tomcat 5.0 Proposal

[Shailendra Singh Negi]

[x] +1 I support the proposal, and will help implement it
[ ] +0 I support the proposal
[ ] -0 I do not support the proposal
[ ] -1 I am against the proposal being implemented, because:





-Shailendra

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [VOTE] Apache Tomcat 5.0 Proposal

[Ben Galbraith]

[X] +1 I support the proposal, and will help implement it
[ ] +0 I support the proposal
[ ] -0 I do not support the proposal
[ ] -1 I am against the proposal being implemented, because:




Long time user, first time voter.  Looking forward to coding and writing 
documentation for Tomcat 4.x and Tomcat 5.x.  Does anyone have any 
specific projects looking for a worker or should I just peruse bugzilla 
and jump in?

Ben Galbraith


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: [VOTE] Apache Tomcat 5.0 Proposal

[Ignacio J. Ortega]

+1

Saludos ,
Ignacio J. Ortega


> -Mensaje original-
> De: Remy Maucherat [mailto:[EMAIL PROTECTED]]
> Enviado el: 3 de julio de 2002 1:57
> Para: Tomcat Developers List
> Asunto: [VOTE] Apache Tomcat 5.0 Proposal
> 
> 
> After trying to address the concerns raised by the proposal draft, I 
> would like to call for a vote on it, now that the discussions 
> have died 
> down.
> 
> 
> [ ] +1 I support the proposal, and will help implement it
> [ ] +0 I support the proposal
> [ ] -0 I do not support the proposal
> [ ] -1 I am against the proposal being implemented, because:
> 
> 
> 
> 
> The vote will run for one full week until July 9th. Users and other 
> contributors may vote, but only committers have binding votes.
> 
> Remy
> 

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [VOTE] Apache Tomcat 5.0 Proposal

[Ben Galbraith]

+1 on proposal.

I have a lot of interested in coding and/or writing documentation for 
Tomcat 5.0.  I'll look for opportunities to jump in, but if someone has 
any Tomcat 4.x or Tomcat 5 projects awaiting a coder or a tech. writer, 
please do let me know.

On Tuesday, July 2, 2002, at 05:57  PM, Remy Maucherat wrote:

> After trying to address the concerns raised by the proposal draft, I 
> would like to call for a vote on it, now that the discussions have died 
> down.
>
> 
> [ ] +1 I support the proposal, and will help implement it
> [ ] +0 I support the proposal
> [ ] -0 I do not support the proposal
> [ ] -1 I am against the proposal being implemented, because:
>
>
> 
>
> The vote will run for one full week until July 9th. Users and other 
> contributors may vote, but only committers have binding votes.
>
> Remy
>
>
> Proposal for Apache Tomcat 5.0
> ==
>
>
>
> Introduction:
> 
>
> This document is a proposal for the next major release of Apache Tomcat,
> Apache Tomcat 5.0.
>
> Apache Tomcat 5.0 will improve on the Apache Tomcat 3.3 and Apache
> Tomcat 4.1 architectures, by making them simpler, more flexible and more
> modular, while at the same time adding support for the new Servlet API 
> 2.4 and
> JSP 2.0 specifications, currently under development by the Java 
> Community
> Process.
>
> The major goals for Apache Tomcat 5.0 are to:
> - improve scalability, reliability and performance over previous 
> versions
> - have simpler/cleaner code, so more people can get involved
> - merge of the various ideas in 3.x and 4.x
> - get the community togheter
> - provide maximum modularity and compliance to the standards
> - make it easy to continue to maintain the existing codebases
>
> Testing will occur to make sure the stated robustness and performance 
> goals
> are met by Tomcat 5.0.
>
> This proposal also tries to take advantage of the lessons learned while
> optimizing and maintaining Tomcat.
>
> Note: The development of Apache Tomcat 4.1.x will continue in parallel 
> to the
> implementation of this proposal.
>
>
>
> General architecture:
> 
>
>
> An improved version of Coyote 1.0, called Coyote 2.0, will be used as
> the Apache Tomcat 5.0 core.
>
> Coyote is currently considered a connector for Tomcat 3.3 and 4.x, and 
> is under
> development in the jakarta-tomcat-connectors repository.
>
> Coyote 1.0 includes:
> - Protocol handlers for AJP 1.3, HTTP/1.1 and JNI
> - Adapter for Tomcat 3.3
> - Adapter for Tomcat 4.x
>
> Extensibility capabilities will be added to Coyote, as well as JMX 
> management
> features, and if possible, addional protocol handlers (like WARP 1.0).
>
> The Servlet API 2.4 specification will be implemented in a new version 
> of
> Catalina, called Catalina 2.0. A new version of the Coyote adapter will 
> be
> written for it if mandated by API changes. Components which duplicate
> functionality provided by Coyote will be removed, including the old 
> connectors.
>
> On the JSP side, Jasper 2 will be updated to support JSP 2.0, will be 
> renamed
> to Jasper 3, and is the proposed Jasper codebase. It provides many
> improvements over Jasper 1 included in Tomcat 3.x and Tomcat 4.0.x, 
> including
> good tag library handling, and near zero overhead when compared to
> an equivalent hand coded servlet. Jasper 2 will also undergo additional
> optimizations.
>
> Apache Tomcat 5.0 will be made by default of the following components:
> - Coyote 2.0 - core
> - Catalina 2.0 - Servlet API 2.4 implementation
> - Jasper 2 - JSP 2.0 implementation
>
> Many other configurations are also possible, and it is expected that 
> advanced
> users take advantage of it to make Tomcat better suit their needs. It 
> is also
> possible that new special purpose components, like a bare bones Servlet 
> API
> implementation, be developed to address the embedded market.
>
> Due to the scope of this work, this initial Proposal only plans
> the implementation and support of the default configuration described 
> above.
>
>
>
> Changes over Apache Tomcat 4.1.x:
> 
>
>
> A lot of the Apache Tomcat 5.0 code will be based on the Apache Tomcat 
> 4.1.x
> codebase. Tomcat 5.0 will also be able to use the Tomcat 3.3.x code.
>
> The following major changes and additions are proposed to the current 
> Apche
> Tomcat code, and related dependencies:
>
> A) Removal of the org.apache.catalina.connector.*
>
> This package is currently deprecated in Tomcat 4.1 because of
> its implementation inefficiencies, and general bad design. It is thus 
> proposed
> that it is removed in Tomcat 5.0.
>
> B) Addition of new loader code for the commons-daemon subproject
>
> It is proposed that, in an attempt to solve the problems with using 
> startup
> scripts, as well as adding additional features oriented towards 
> reliability
> (including the capability to restart Tomcat automatically should the JVM
> cra

Re: [VOTE] Apache Tomcat 5.0 Proposal

[Bojan Smojver]

On Wed, 2002-07-03 at 09:57, Remy Maucherat wrote:

> 
> [ ] +1 I support the proposal, and will help implement it
> [X] +0 I support the proposal
> [ ] -0 I do not support the proposal
> [ ] -1 I am against the proposal being implemented, because:
> 

Which might actually turn out to be +0.01 ;-)

Bojan


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [VOTE] Apache Tomcat 5.0 Proposal

[Bill Barker]

> 
> [X] +1 I support the proposal, and will help implement it
> [ ] +0 I support the proposal
> [ ] -0 I do not support the proposal
> [ ] -1 I am against the proposal being implemented, because:
> 
> 
> 



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [VOTE] Apache Tomcat 5.0 Proposal

[Denis Benoit]

On Tue, 2 Jul 2002, Remy Maucherat wrote:

> After trying to address the concerns raised by the proposal draft, I 
> would like to call for a vote on it, now that the discussions have died 
> down.
> 
> 
> [X] +1 I support the proposal, and will help implement it
> [ ] +0 I support the proposal
> [ ] -0 I do not support the proposal
> [ ] -1 I am against the proposal being implemented, because:
> 
> 
> 
> 
> The vote will run for one full week until July 9th. Users and other 
> contributors may vote, but only committers have binding votes.
> 
> Remy
> 

-- 
Denis Benoit
[EMAIL PROTECTED]


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [VOTE] Apache Tomcat 5.0 Proposal

[Pier Fumagalli]

Remy Maucherat <[EMAIL PROTECTED]> wrote:

> 
> [ ] +1 I support the proposal, and will help implement it
> [X] +0 I support the proposal
> [ ] -0 I do not support the proposal
> [ ] -1 I am against the proposal being implemented, because:
> 

As long as the interfaces don't change too much (especially, Container and
Component, all the rest I don't care). We started out process of stripping
out "for good" all the stuff distributed with TC4x, working on some new
startup classes and so on (and looking over at the excellent work made by
MinTC, and what Scarab is doing on that front)...

If you want to be flamed heavily check out 

Pier

--
[Perl] combines all the worst aspects of C and Lisp:  a billion of different
sublanguages in  one monolithic executable.  It combines the power of C with
the readability of PostScript. [Jamie Zawinski - DNA Lounge - San Francisco]


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [VOTE] Apache Tomcat 5.0 Proposal

[Bob Herrmann]

On Tue, 2002-07-02 at 19:57, Remy Maucherat wrote:
> After trying to address the concerns raised by the proposal draft, I 
> would like to call for a vote on it, now that the discussions have died 
> down.
> 
> 
> [X] +1 I support the proposal, and will help implement it
> [ ] +0 I support the proposal
> [ ] -0 I do not support the proposal
> [ ] -1 I am against the proposal being implemented, because:

Willing to help in any way I can.

Cheers,
-bob




--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [VOTE] Apache Tomcat 5.0 Proposal

[jean-frederic clere]

+1

Remy Maucherat wrote:
> After trying to address the concerns raised by the proposal draft, I 
> would like to call for a vote on it, now that the discussions have died 
> down.
> 
> 
> [ ] +1 I support the proposal, and will help implement it
> [ ] +0 I support the proposal
> [ ] -0 I do not support the proposal
> [ ] -1 I am against the proposal being implemented, because:
> 
> 
> 
> 
> The vote will run for one full week until July 9th. Users and other 
> contributors may vote, but only committers have binding votes.
> 
> Remy
> 
> 
> 
> 
> 
> 
> Proposal for Apache Tomcat 5.0
> ==
> 
> 
> 
> Introduction:
> 
> 
> This document is a proposal for the next major release of Apache Tomcat, 
> Apache Tomcat 5.0.
> 
> Apache Tomcat 5.0 will improve on the Apache Tomcat 3.3 and Apache
> Tomcat 4.1 architectures, by making them simpler, more flexible and more 
> modular, while at the same time adding support for the new Servlet API 2.4 and
> JSP 2.0 specifications, currently under development by the Java Community 
> Process.
> 
> The major goals for Apache Tomcat 5.0 are to:
> - improve scalability, reliability and performance over previous versions
> - have simpler/cleaner code, so more people can get involved
> - merge of the various ideas in 3.x and 4.x
> - get the community togheter
> - provide maximum modularity and compliance to the standards
> - make it easy to continue to maintain the existing codebases
> 
> Testing will occur to make sure the stated robustness and performance goals
> are met by Tomcat 5.0.
> 
> This proposal also tries to take advantage of the lessons learned while 
> optimizing and maintaining Tomcat.
> 
> Note: The development of Apache Tomcat 4.1.x will continue in parallel to the 
> implementation of this proposal.
> 
> 
> 
> General architecture:
> 
> 
> 
> An improved version of Coyote 1.0, called Coyote 2.0, will be used as 
> the Apache Tomcat 5.0 core.
> 
> Coyote is currently considered a connector for Tomcat 3.3 and 4.x, and is under
> development in the jakarta-tomcat-connectors repository.
> 
> Coyote 1.0 includes:
> - Protocol handlers for AJP 1.3, HTTP/1.1 and JNI
> - Adapter for Tomcat 3.3
> - Adapter for Tomcat 4.x
> 
> Extensibility capabilities will be added to Coyote, as well as JMX management
> features, and if possible, addional protocol handlers (like WARP 1.0).
> 
> The Servlet API 2.4 specification will be implemented in a new version of 
> Catalina, called Catalina 2.0. A new version of the Coyote adapter will be
> written for it if mandated by API changes. Components which duplicate 
> functionality provided by Coyote will be removed, including the old connectors.
> 
> On the JSP side, Jasper 2 will be updated to support JSP 2.0, will be renamed 
> to Jasper 3, and is the proposed Jasper codebase. It provides many 
> improvements over Jasper 1 included in Tomcat 3.x and Tomcat 4.0.x, including 
> good tag library handling, and near zero overhead when compared to 
> an equivalent hand coded servlet. Jasper 2 will also undergo additional 
> optimizations.
> 
> Apache Tomcat 5.0 will be made by default of the following components:
> - Coyote 2.0 - core
> - Catalina 2.0 - Servlet API 2.4 implementation
> - Jasper 2 - JSP 2.0 implementation
> 
> Many other configurations are also possible, and it is expected that advanced
> users take advantage of it to make Tomcat better suit their needs. It is also
> possible that new special purpose components, like a bare bones Servlet API 
> implementation, be developed to address the embedded market.
> 
> Due to the scope of this work, this initial Proposal only plans 
> the implementation and support of the default configuration described above.
> 
> 
> 
> Changes over Apache Tomcat 4.1.x:
> 
> 
> 
> A lot of the Apache Tomcat 5.0 code will be based on the Apache Tomcat 4.1.x 
> codebase. Tomcat 5.0 will also be able to use the Tomcat 3.3.x code.
> 
> The following major changes and additions are proposed to the current Apche
> Tomcat code, and related dependencies:
> 
> A) Removal of the org.apache.catalina.connector.*
> 
> This package is currently deprecated in Tomcat 4.1 because of 
> its implementation inefficiencies, and general bad design. It is thus proposed
> that it is removed in Tomcat 5.0.
> 
> B) Addition of new loader code for the commons-daemon subproject
> 
> It is proposed that, in an attempt to solve the problems with using startup 
> scripts, as well as adding additional features oriented towards reliability
> (including the capability to restart Tomcat automatically should the JVM
> crashes or experience memory management related problems), the launcher code
> which will be developed as part of commons-daemon be adopted.
> This code will be based in part on the launcher code used for the Sun Web
> S

Re: [VOTE] Apache Tomcat 5.0 Proposal

[Henri Gomez]

> As long as the interfaces don't change too much (especially, Container and
> Component, all the rest I don't care). We started out process of stripping
> out "for good" all the stuff distributed with TC4x, working on some new
> startup classes and so on (and looking over at the excellent work made by
> MinTC, and what Scarab is doing on that front)...
> 
> If you want to be flamed heavily check out 

Welcome to Jerry ;)

BTW, emulation is allways great till it didn't turn in flam wars.

I'll try to track both TC 5.0 and Jerry 


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [VOTE] Apache Tomcat 5.0 Proposal

[Kin-Man Chung]

+1.

I'll populate jasper2 and servlet-api with initial changes for JSP2.0
support.


> Date: Tue, 02 Jul 2002 16:57:20 -0700
> From: Remy Maucherat <[EMAIL PROTECTED]>
> Subject: [VOTE] Apache Tomcat 5.0 Proposal
> To: Tomcat Developers List <[EMAIL PROTECTED]>
>
> After trying to address the concerns raised by the proposal draft, I 
> would like to call for a vote on it, now that the discussions have died 
> down.
> 
> 
> [ ] +1 I support the proposal, and will help implement it
> [ ] +0 I support the proposal
> [ ] -0 I do not support the proposal
> [ ] -1 I am against the proposal being implemented, because:
> 
> 
> 
> 
> The vote will run for one full week until July 9th. Users and other 
> contributors may vote, but only committers have binding votes.
> 
> Remy


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [VOTE] Apache Tomcat 5.0 Proposal

[Christopher K. St. John]

 Probably a little late:

> >
> > [X] +1 I support the proposal, and will help implement it
> > [ ] +0 I support the proposal
> > [ ] -0 I do not support the proposal
> > [ ] -1 I am against the proposal being implemented, because:
> >

 Actually, I'm probably closer to a +0 for the next few weeks,
slowly transitioning back into being able to help implement
after that.


-- 
Christopher St. John [EMAIL PROTECTED]
DistribuTopia http://www.distributopia.com

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: [VOTE] Apache Tomcat 5.0 Proposal

[Amy Roh]

Sorry for the late vote.  I've been on vacation for last two weeks.

But for the record, you have my +1.

Thanks,
Amy

Remy Maucherat wrote:

> After trying to address the concerns raised by the proposal draft, I
> would like to call for a vote on it, now that the discussions have died
> down.
>
> 
> [ ] +1 I support the proposal, and will help implement it
> [ ] +0 I support the proposal
> [ ] -0 I do not support the proposal
> [ ] -1 I am against the proposal being implemented, because:
>
> 
>
> The vote will run for one full week until July 9th. Users and other
> contributors may vote, but only committers have binding votes.
>
> Remy
>
>   
>
> Proposal for Apache Tomcat 5.0
> ==
>
> Introduction:
> 
>
> This document is a proposal for the next major release of Apache Tomcat,
> Apache Tomcat 5.0.
>
> Apache Tomcat 5.0 will improve on the Apache Tomcat 3.3 and Apache
> Tomcat 4.1 architectures, by making them simpler, more flexible and more
> modular, while at the same time adding support for the new Servlet API 2.4 and
> JSP 2.0 specifications, currently under development by the Java Community
> Process.
>
> The major goals for Apache Tomcat 5.0 are to:
> - improve scalability, reliability and performance over previous versions
> - have simpler/cleaner code, so more people can get involved
> - merge of the various ideas in 3.x and 4.x
> - get the community togheter
> - provide maximum modularity and compliance to the standards
> - make it easy to continue to maintain the existing codebases
>
> Testing will occur to make sure the stated robustness and performance goals
> are met by Tomcat 5.0.
>
> This proposal also tries to take advantage of the lessons learned while
> optimizing and maintaining Tomcat.
>
> Note: The development of Apache Tomcat 4.1.x will continue in parallel to the
> implementation of this proposal.
>
> General architecture:
> 
>
> An improved version of Coyote 1.0, called Coyote 2.0, will be used as
> the Apache Tomcat 5.0 core.
>
> Coyote is currently considered a connector for Tomcat 3.3 and 4.x, and is under
> development in the jakarta-tomcat-connectors repository.
>
> Coyote 1.0 includes:
> - Protocol handlers for AJP 1.3, HTTP/1.1 and JNI
> - Adapter for Tomcat 3.3
> - Adapter for Tomcat 4.x
>
> Extensibility capabilities will be added to Coyote, as well as JMX management
> features, and if possible, addional protocol handlers (like WARP 1.0).
>
> The Servlet API 2.4 specification will be implemented in a new version of
> Catalina, called Catalina 2.0. A new version of the Coyote adapter will be
> written for it if mandated by API changes. Components which duplicate
> functionality provided by Coyote will be removed, including the old connectors.
>
> On the JSP side, Jasper 2 will be updated to support JSP 2.0, will be renamed
> to Jasper 3, and is the proposed Jasper codebase. It provides many
> improvements over Jasper 1 included in Tomcat 3.x and Tomcat 4.0.x, including
> good tag library handling, and near zero overhead when compared to
> an equivalent hand coded servlet. Jasper 2 will also undergo additional
> optimizations.
>
> Apache Tomcat 5.0 will be made by default of the following components:
> - Coyote 2.0 - core
> - Catalina 2.0 - Servlet API 2.4 implementation
> - Jasper 2 - JSP 2.0 implementation
>
> Many other configurations are also possible, and it is expected that advanced
> users take advantage of it to make Tomcat better suit their needs. It is also
> possible that new special purpose components, like a bare bones Servlet API
> implementation, be developed to address the embedded market.
>
> Due to the scope of this work, this initial Proposal only plans
> the implementation and support of the default configuration described above.
>
> Changes over Apache Tomcat 4.1.x:
> 
>
> A lot of the Apache Tomcat 5.0 code will be based on the Apache Tomcat 4.1.x
> codebase. Tomcat 5.0 will also be able to use the Tomcat 3.3.x code.
>
> The following major changes and additions are proposed to the current Apche
> Tomcat code, and related dependencies:
>
> A) Removal of the org.apache.catalina.connector.*
>
> This package is currently deprecated in Tomcat 4.1 because of
> its implementation inefficiencies, and general bad design. It is thus proposed
> that it is removed in Tomcat 5.0.
>
> B) Addition of new loader code for the commons-daemon subproject
>
> It is proposed that, in an attempt to solve the problems with using startup
> scripts, as well as adding additional features oriented towards reliability
> (including the capability to restart Tomcat automatically should the JVM
> crashes or experience memory management related problems), the launcher code
> which will be developed as part of commons-daemon be adopted.
> This code will be based in part on the launche