You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by cr...@locus.apache.org on 2000/04/07 01:13:34 UTC
cvs commit: jakarta-tomcat RELEASE-PLAN-3.2 STATUS.html
craigmcc 00/04/06 16:13:34
Added: . RELEASE-PLAN-3.2 STATUS.html
Log:
Add initial cracks at two new documents -- nothing here is authoritative
until discussed and agreed to by the TOMCAT-DEV community.
"RELEASE-PLAN-3.2" is a prototype document for the release plan (schedule)
for the next version. It will be renamed RELEASE-PLAN once we are through
with the current one, which is (naturally enough) for 3.1. You can see
that I have not tried to identify any specific functionality to be
scheduled for particular releases, but I've laid out a proposed schedule
that gets us to final release by JavaOne 2000.
"STATUS.html" is an accumulation of action items that I've heard, or
talked to people about, that might be interested to add to Tomcat in
version 3.2 or some later version. The idea is that people volunteer
to work on one or more of these items, and the interested parties discuss
how to do it (on TOMCAT-DEV so other folks can see what's being thought of
and discussed), and then perform the changes.
A TOMCAT-DEV announcement about these two files will be sent in a couple
of minutes.
Revision Changes Path
1.1 jakarta-tomcat/RELEASE-PLAN-3.2
Index: RELEASE-PLAN-3.2
===================================================================
$Id: RELEASE-PLAN-3.2,v 1.1 2000/04/06 23:13:34 craigmcc Exp $
NOTE: This document is the first cut at a release plan for the next
dot release of Tomcat. Nothing in this document should be
considered authoritative until it has been discussed and approved
on the TOMCAT-DEV mailing list, at which point this note will
be removed.
Tomcat 3.2 Release Plan
=======================
Objective:
The objective of the 3.2 release is to continue the improvement
in quality, performance, and functionality of the Tomcat servlet
container, enabling us to deliver a high quality, production ready,
release by JavaOne 2000.
The Tomcat 3.2 release cycle has two intermediate milestones (with
"burn in" periods for both), after which it will be qualified as
Beta. The target release date for the final release is June 5, 2000.
Tomcat 3.2 Milestone 1 Release:
Code Freeze/Tag Date: April 21, 2000
Release Manager: ???
The following action items from the STATUS.html file shall be
completed and tested for this release:
TODO - copy agreed upon items from the status file
Tomcat 3.2 Milestone 2 Release:
Code Freeze/Tag Date: May 5, 2000
Release Manager: ???
The following action items from the STATUS.html file shall be
completed and tested for this release:
TODO - copy agreed upon items from the status file
Tomcat 3.2 Beta Release:
Code Freeze/Tag Date: May 19, 2000
Release Manager: ???
At this point, development of new features on the main CVS branch
should be suspended, and the focus changed to fixing outstanding
bugs in preparation for the final release.
Tomcat 3.2 Final Release
Code Freeze Date: June 2, 2000
Final Tag and Release: June 5, 2000
Release Manager: ???
After the final release is tagged, the main CVS branch is opened
again for enhancements and changes targeted at future releases.
1.1 jakarta-tomcat/STATUS.html
Index: STATUS.html
===================================================================
<html>
<head>
<title>Action Items List for Jakarta Tomcat</title>
</head>
<body bgcolor="white">
<div align="center">
NOTE: This document is the first cut at a status document<br>
to track outstanding issues for the ongoing development of<br>
Tomcat. Nothing in this document should be considered<br>
authoritative until it has been discussed and initially<br>
approved on the TOMCAT-DEV mailing list, at which point<br>
this note will be removed.
</div>
<div align="center"><h1>Action Items List for Jakarta Tomcat</h1></div>
<p>This document is a living list of the action items related to the
current and future development of the Tomcat servlet container. As such,
it focuses primarily on enhancements to existing features, as well as the
addition of new features. Bugs in the implementation of existing features
should be reported to
<a href="http://jakarta.apache.org/bugs">http://jakarta.apache.org/bugs</a>
so that they can be tracked and fixed. The columns in this report contain
the following information:
<ul>
<li><b>Priority</b> - A sense of how important the Tomcat development
community feels it is to address this issue in the short term.</li>
<li><b>Release</b> - The interim or final release (such as <code>3.2m2</code>)
for which this action item is scheduled to be completed.</li>
<li><b>Action Item</b> - Concise description of the action item
to be completed.</li>
<li><b>Volunteers</b> - Names and EMAIL addresses of those developers who
have volunteered to assist in the design, implementation, testing, and
documentation of this action item's changes to Tomcat.</li>
</ul>
<p>Additions to, subtractions from, and changes to the action items listed
here should be discussed and approved on the TOMCAT-DEV mailing list, as
described on the
<a href="http://jakarta.apache.org/guidelines/decisions.html">Decision
Making</a> page on the Jakarta Project web site. Developers can nominate
themselves to work on particular action items by asking a Committer to add
their name and EMAIL address to those items. The developers working on each
item should discuss and agree upon the approach to be used for implementing
the item's changes to the project source code and documentation, prior to
completing those changes. Such discussions should take place on the
TOMCAT-DEV mailing list so that everyone can stay apprised of what is going
on, or chime in if they want to contribute ideas and suggestions.
<p>At various points in time, particular action items will be selected
and assigned to a particular interim release of Tomcat (based on lazy consensus
on the TOMCAT-DEV mailing list). At that time, the assigned release will be
recorded in this document, and the item will be listed under that release in
the current <a href="RELEASE-PLAN-3.2">RELEASE-PLAN</a> schedule.
<p>For convenience, the action items have been organized into general
categories, which are presented in alphabetical order. The following
categories of actions are currently identified:
<ul>
<li><a href="#Architecture">Architecture</a> of major Tomcat components
<li><a href="#Administration">Administration</a> application and tools
<li><a href="#Connectors">Connectors</a> to web servers and HTTP clients
<li><a href="#Containers">Containers</a> in the Tomcat core engine
<li><a href="#JSP">JSP</a> functionality enhancements
<li><a href="#Servlet">Servlet</a> functionality enhancements
</ul>
<p>NOTE: In addition to this list of action items related to the main CVS
source branch for the <code>jakarta-tomcat</code> subproject, a number of
people have expressed interest in working on the <i>Catalina</i> architecture.
To facilitate tracking of these efforts, a
<a href="proposals/catalina/STATUS.html">separate STATUS document</a>
is maintained in the <code>proposals/catalina</code> subdirectory.
<br><br>
<div align="center"><hr width="75%"</div>
<br>
<a name="Architecture"></a>
<div align="center"><h1>Architecture</h1></div>
<table border="1" width="100%">
<tr>
<th width="10%">Priority</th>
<th width="10%">Release</th>
<th width="50%">Action Item</th>
<th width="30%">Volunteers</th>
</tr>
<tr>
<td>High</td>
<td>---</td>
<td>Define a Tomcat-specific <i>Service Provider Interface</i> (SPI)
that defines a stable API which application server and development
tool providers can use to integrate Tomcat within their products.</td>
<td><a href="mailto:Craig.McClanahan@eng.sun.com">Craig McClanahan</a></td>
</tr>
<tr>
<td>Medium</td>
<td>----</td>
<td>Discuss and agree upon the outlines of the architecture for the
core servlet container components of the next major release (4.0)
of Tomcat, which will correspond to the next versions of the Servlet
and JSP APIs.</td>
<td><a href="mailto:Craig.McClanahan@eng.sun.com">Craig McClanahan</a></td>
</tr>
<tr>
<td>Medium</td>
<td>---</td>
<td>Discuss and agree upon the outlines of the architecture for the
JSP page compiler and execution environment for the next major
release (4.0) of Tomcat, which will correspond to the next versions
of the Servlet and JSP APIs.</td>
<td>---</td>
</tr>
<tr>
<td>Low</td>
<td>---</td>
<td>Discuss and agree upon Tomcat distribution strategies so that users
can select a minimal "reference implementation" version of Tomcat to
validate their own containers against, or a full featured release
with all currently included functionality.</td>
<td>---</td>
</tr>
</table>
<a name="Administration"></a>
<div align="center"><h1>Administration</h1></div>
<table border="1" width="100%">
<tr>
<th width="10%">Priority</th>
<th width="10%">Release</th>
<th width="50%">Action Item</th>
<th width="30%">Volunteers</th>
</tr>
<tr>
<td>High</td>
<td>---</td>
<td>Add out-of-the-box functionality to install Tomcat as a
"service" under Microsoft NT.</td>
<td>---</td>
</tr>
<tr>
<td>High</td>
<td>---</td>
<td>Improve the ease of installation of Tomcat, especially on
Windows platforms by integrating it with an installation program.</td>
<td>---</td>
</tr>
<tr>
<td>Medium</td>
<td>---</td>
<td>Define functional and user interface requirements for the interactive
(servlet/JSP based) administration tool for managing running Tomcat
instances.</td>
<td>---</td>
</tr>
<tr>
<td>Medium</td>
<td>---</td>
<td>Implement interactive administration tool that fulfills the
requirements described above.</td>
<td>---</td>
</tr>
<tr>
<td>Low</td>
<td>---</td>
<td>Design an implement a tool for creating and customizing web application
deployment descriptors (i.e. <code>web.xml</code> files) in a
user friendly manner.</td>
<td>---</td>
</tr>
</table>
<a name="Connectors"></a>
<div align="center"><h1>Connectors</h1></div>
<table border="1" width="100%">
<tr>
<th width="10%">Priority</th>
<th width="10%">Release</th>
<th width="50%">Action Item</th>
<th width="30%">Volunteers</th>
</tr>
<tr>
<td>High</td>
<td>---</td>
<td>Improve the performance and thread utilization of the
current HTTP/1.0 connector used by Tomcat stand-alone.</td>
<td>---</td>
</tr>
<tr>
<td>Medium</td>
<td>---</td>
<td>Design, implement, and test an HTTP/1.1 connector to be
used by Tomcat stand-alone.</td>
<td>---</td>
</tr>
<tr>
<td>Medium</td>
<td>---</td>
<td>Implement a two-way communications protocol in the Apache
connector, such that getRealPath() can respect Apache virtual
mappings, getMimeType() can respect Apache MIME type mappings,
and so on.</td>
<td>---</td>
</tr>
<tr>
<td>Medium</td>
<td>---</td>
<td>Implement a new Apache/2.0 connector whereby Tomcat can be
run "in process" instead of "out of process".</td>
<td><a href="mailto:Costin.Manolache@eng.sun.com">Costin Manolache</a></td>
</tr>
<tr>
<td>Medium</td>
<td>---</td>
<td>Ensure that all web server connectors pass sufficient information to
properly set the value returned by
<code>ServletRequest.isSecure()</code> and to populate the SSL
information attributes described in ...</td>
<td>---</td>
</tr>
</table>
<a name="Containers"></a>
<div align="center"><h1>Containers</h1></div>
<table border="1" width="100%">
<tr>
<th width="10%">Priority</th>
<th width="10%">Release</th>
<th width="50%">Action Item</th>
<th width="30%">Volunteers</th>
</tr>
<tr>
<td>High</td>
<td>---</td>
<td>Define and implement full virtual host support, including:
single-JVM configuration option, support for per-virtual-host
interceptors, and so on.</td>
<td>---</td>
</tr>
<tr>
<td>High</td>
<td>---</td>
<td>Finish the implementation and testing of FORM-based authentication
and access control.</td>
<td>---</td>
</tr>
<tr>
<td>Medium</td>
<td>---</td>
<td>Design and implement DIGEST based authentication and access
control.</td>
<td>---</td>
</tr>
<tr>
<td>Medium</td>
<td>---</td>
<td>Design and implement SSL based authentication and access
control, in a manner that minimizes installation hassles and
does not cause problems with US export controls.</td>
<td>---</td>
</tr>
<tr>
<td>Medium</td>
<td>---</td>
<td>Design and implement "single sign on" support for cross application
access with a single login, as described in Section 11 of the
Servlet API Specification Version 2.2.</td>
<td>---</td>
</tr>
<tr>
<td>Medium</td>
<td>---</td>
<td>Design and implement support for serving web applications
directly from WAR files, and/or from a URL-based document
root. Probably requires pluggable implementation of the
getResource() family of calls.</td>
<td>---</td>
</tr>
<tr>
<td>Medium</td>
<td>---</td>
<td>Refactor the implementation of RequestSecurityProvider and
SecurityCheck so that a Tomcat deployer can integrate with
their own security realm by implementing a single class,
rather than having to duplicate the code in SecurityCheck.</td>
<td>---</td>
</tr>
<tr>
<td>Medium</td>
<td>---</td>
<td>Add support for pluggable session management components, with
support for file-based, JDBC-based, JNDI-based, and possibly
other persistence mechanisms.</td>
<td>---</td>
</tr>
<tr>
<td>Medium</td>
<td>---</td>
<td>Improve the internationalization support provided in Tomcat by
factoring remaining hard-coded English message strings into
resource files, and providing translated resource files for
other languages.</td>
<td>---</td>
</tr>
<tr>
<td>Medium</td>
<td>---</td>
<td>Implement the optional <i>web application environment</i> support
described in Section 9.9 of the Servlet API Specification Version 2.2,
and Chapter 5 of the Java2 Platform Enterprise Edition Version 1.2
Specification.</td>
<td>---</td>
</tr>
<tr>
<td>Medium</td>
<td>---</td>
<td>More generalized implementation of logging, that allows plugins
for choosing log formatting styles.</td>
<td>---</td>
</tr>
<tr>
<td>Medium</td>
<td>---</td>
<td>Design and implement better mechanisms for Tomcat to "sandbox"
multiple web applications running in the same container, to avoid
having them interfere with each other.</td>
<td>---</td>
</tr>
<tr>
<td>Low</td>
<td>---</td>
<td>Implement instance pooling for servlets that implement the
<code>SingleThreadModel</code> interface.</td>
<td>---</td>
</tr>
<tr>
<td>Low</td>
<td>---</td>
<td>Fully support "absolute" document root paths on Windows that
start with a '/' or '\' character, instead of a drive letter
plus a colon. Currently, <code>File.isAbsolute()</code> on
Windows JVMS considers such a path to be relative.</td>
<td>---</td>
</tr>
</table>
<a name="JSP"></a>
<div align="center"><h1>JSP Functionality</h1></div>
<table border="1" width="100%">
<tr>
<th width="10%">Priority</th>
<th width="10%">Release</th>
<th width="50%">Action Item</th>
<th width="30%">Volunteers</th>
</tr>
<tr>
<td>Medium</td>
<td>---</td>
<td>Incorporate support for pluggable JSP page parsers.</td>
<td>---</td>
</tr>
<tr>
<td>Medium</td>
<td>---</td>
<td>Incorporate support for scripting languages other than Java,
as outlined in the JSP specification.</td>
<td>---</td>
</tr>
<tr>
<td>Medium</td>
<td>---</td>
<td>Review and optimize the performance of the servlet classes
generated by the JSP page compiler.</td>
<td>---</td>
</tr>
</table>
<a name="Servlet"></a>
<div align="center"><h1>Servlet Functionality</h1></div>
<table border="1" width="100%">
<tr>
<th width="10%">Priority</th>
<th width="10%">Release</th>
<th width="50%">Action Item</th>
<th width="30%">Volunteers</th>
</tr>
<tr>
<td>High</td>
<td>---</td>
<td>Add full support for WebDAV, either as servlets included in the
full-featured distribution of Tomcat, or as a separate sub-project
under Jakarta.</td>
<td>---</td>
</tr>
<tr>
<td>Medium</td>
<td>---</td>
<td>Default file-serving servlet has problems dealing with directory and
file names that contain spaces or other special characters.
[Bug ID#10, 101].</td>
<td>---</td>
</tr>
<tr>
<td>Low</td>
<td>---</td>
<td>Integrate the <a href="http://java.apache.org/jservssi">Apache JSSI</a>
project's support for embedded <code><servlet></code> tags in
<code>.jhtml</code> pages into the full-featured distribution of
Tomcat (assuming the Apache JSSI project group agrees), bringing it
up to date with respect to servlet API 2.2 as required.</td>
<td>---</td>
</tr>
<tr>
<td>Low</td>
<td>---</td>
<td>Add a default servlet that can serve CGI scripts and applications,
for use in Tomcat deployments not connected to a web server, or
to enable RequestDispatcher-based access to CGI scripts and
applications.</td>
<td>---</td>
</tr>
</table>
<br>
<div align="center"><hr width="75%"><font size="2">
$Id: STATUS.html,v 1.1 2000/04/06 23:13:34 craigmcc Exp $
</font></div>
</body>
</html>