Punky Tse wrote:
3) How about putting all the installation and configuration of Tomcat
standalone first, and then followed by some chapters (advanced topics)
about
Running Tomcat behind web servers?
It's already organized that way. See the first paragraph of the
editorial notes:
I think
P.S. What hacker I mean is: The one who read the source code and make
change to it so that the whole system get benefit from it. So you are
hacker. (but me not yet). The guy who break the system is
cracker, or black
hacker to be specific.
??? A cracker is a criminal hacker. not someone
P.S. What hacker I mean is: The one who read the source code and make
change to it so that the whole system get benefit from it. So you are
hacker. (but me not yet). The guy who break the system is
cracker, or black
hacker to be specific.
??? A cracker is a criminal hacker. not
2) How about moving Developing Interceptors, Valves and Connectors, and
Using Tomcat Utility Classes to a seperate Developer Guide?
They are only
useful for real hackers.
Don't forget what make Apache HTTP server so successfull.
The number of modules built for Apache 1.2/1.3 APIs.
If we don't
, July 10, 2001 4:37 AM
To: [EMAIL PROTECTED]
Subject: [DOC] Table of Contents
OK, at Craig's request, here's the current Table of Contents for Tomcat
docs. (I wrote a program to convert *** to 1.2.3. format so it's easier
to read.)
It just occured to me that maybe the TOC will be applicable
Martin van den Bemt wrote:
I'm missing a very important one : servlet debugging. All the development
environments support jps debugging, but servlet debugging is still a pain..
So that could need some explenation..
See
http://www.jguru.com/faq/view.jsp?EID=158
I've added it to the TOC.
3) How about putting all the installation and configuration of Tomcat
standalone first, and then followed by some chapters (advanced topics)
about
Running Tomcat behind web servers?
It's already organized that way. See the first paragraph of the
editorial notes:
I think there should
, please respond with a separate subject line (like
Copyrights) so we can keep discussions of copyright separate from
discussions of the table of contents itself. The copyright will not
prevent other Apache contributors from using or editing it or adding it
to the code base -- that is, I want
2) How about moving Developing Interceptors, Valves and Connectors, and
Using Tomcat Utility Classes to a seperate Developer Guide?
They are only
useful for real hackers.
Don't forget what make Apache HTTP server so successfull.
The number of modules built for Apache 1.2/1.3 APIs.
If we
source if I were
sure I'd keep my rights to use it too. If anyone can enlighten me on
this topic, please respond with a separate subject line (like
Copyrights) so we can keep discussions of copyright separate from
discussions of the table of contents itself. The copyright will not
prevent other
-
From: Alex Chaffee [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Saturday, July 07, 2001 1:02 AM
Subject: DOC: Table of Contents
Here's my current Table of Contents. As I said in an earlier message,
I'd like to organize this TOC
OK, at Craig's request, here's the current Table of Contents for Tomcat
docs. (I wrote a program to convert *** to 1.2.3. format so it's easier
to read.)
It just occured to me that maybe the TOC will be applicable to both
versions (3 vs 4), even though the content of each chapter
Punky Tse wrote:
Alex,
Please see my comment below:
1) The details of the TOC looks better than my version.
Thanks :)
2) How about moving Developing Interceptors, Valves and Connectors, and
Using Tomcat Utility Classes to a seperate Developer Guide? They are only
useful for real
Here's my current Table of Contents. As I said in an earlier message,
I'd like to organize this TOC as a little more abstract than a simple
table of contents. Each section should be organized to contain not just
our original documents, but also a list of other resources on that
topic
14 matches
Mail list logo
