• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Motivation and Reason for the "How Tomcat Works" book

 
Ko Ko Naing
Ranch Hand
Posts: 3178
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Could you mention your motivation to write this book? What are the main factors that make you write this book?

One more question is that "Why did you choose to write about Tomcat? Why not about JBoss? Why not about other JSP and servlets containers?"

Thanks...
 
Budi Kurniawan
author
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I've been designing and developing servlet/JSP applications for years now. And, naturally, if you like something, at one stage you will start asking questions about it. The questions that came to mind were:
1. What is it that prevents me from changing the value of a request parameter. I knew it was a Map, but how come I could only read it?
2. How does the servlet container know when to invalidate a session? There must be a background thread, but where?
3. How many instances does the container create for each servlet? What is the impact on performance?
4. How does the container parse the web.xml file?
5. How do the Manager and Admin application get access to Catalina so that they can start and stop, deploy and redeploy, an application?

Those sort of things.

So, I began to play with Tomcat code. It was an easy choice because it was popular and, more importantly, the source is available. The more I read it, the more I got interested. And, honestly, I learned a lot.

I decided to write How Tomcat Works to share what I have learned (the hard way) so that those who want to extend Tomcat (or even join the development team) do not have to go through what I did.
 
Ko Ko Naing
Ranch Hand
Posts: 3178
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Budi Kurniawan:
I decided to write How Tomcat Works to share what I have learned (the hard way) so that those who want to extend Tomcat (or even join the development team) do not have to go through what I did.


So your book is like your diary about your past experience on exploration of Tomcat, isn't it?

I do appreciate your great reply about the motivation to write the book.. Thanks...
 
Alvin chew
Ranch Hand
Posts: 834
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
thanks for advices and saving our 10 years learning curve
 
friso dejonge
Ranch Hand
Posts: 162
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I've been designing and developing servlet/JSP applications for years now. And, naturally, if you like something, at one stage you will start asking questions about it. The questions that came to mind were:
1. What is it that prevents me from changing the value of a request parameter. I knew it was a Map, but how come I could only read it?
2. How does the servlet container know when to invalidate a session? There must be a background thread, but where?
3. How many instances does the container create for each servlet? What is the impact on performance?
4. How does the container parse the web.xml file?
5. How do the Manager and Admin application get access to Catalina so that they can start and stop, deploy and redeploy, an application?
Those sort of things.
So, I began to play with Tomcat code. It was an easy choice because it was popular and, more importantly, the source is available. The more I read it, the more I got interested. And, honestly, I learned a lot.
I decided to write How Tomcat Works to share what I have learned (the hard way) so that those who want to extend Tomcat (or even join the development team) do not have to go through what I did.


After reading the reply, the following comes to mind:
With all the experience, did you help writing with the latest release of tomcat ?
 
Sandeep Jindal
Ranch Hand
Posts: 180
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

1. What is it that prevents me from changing the value of a request parameter. I knew it was a Map, but how come I could only read it?
2. How does the servlet container know when to invalidate a session? There must be a background thread, but where?
3. How many instances does the container create for each servlet? What is the impact on performance?
4. How does the container parse the web.xml file?
5. How do the Manager and Admin application get access to Catalina so that they can start and stop, deploy and redeploy, an application?



Hello,

From your answer one thing is very clear, that whenever these questions came into our mind, we wont write book but will read your book.

Regards
 
Ko Ko Naing
Ranch Hand
Posts: 3178
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by friso dejonge:


After reading the reply, the following comes to mind:
With all the experience, did you help writing with the latest release of tomcat ?


ASAIK, Budi and Paul are not in the developement team of Tomcat...

You might wanna have a look at Who We Are list of Tomcat team...
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic