Well a Tomcat will a small memory footprint is also very interesting for me :)
For guidelines on how to use it ?
2005/12/22, Yoav Shapira [EMAIL PROTECTED]:
I'm willing to help...
Yoav
On 12/21/05, Costin Manolache [EMAIL PROTECTED] wrote:
Well, it's not about 'vote' or plans, it's more
but I will need to see if I can work out some time.
Merry Christmas, Allistair.
-Original Message-
From: Henri Gomez [mailto:[EMAIL PROTECTED]
Sent: 22 December 2005 11:12
To: Tomcat Developers List
Subject: Re: Tomcat 6 plans (JSP 2.1)
Well a Tomcat will a small memory footprint is also
Henri Gomez wrote:
Well a Tomcat will a small memory footprint is also very interesting for me :)
How is Tomcat memory usage large ? Personally, I would think it's
extremely reasonable given the feature set, at least when using APR. It
would seem the base Java runtime would completely offset
Remy Maucherat wrote:
Allistair Crossley wrote:
Hi,
Personally I am less interested in a small footprint Tomcat and more
interested in tools that help manage and report on the internals of
Tomcat. Instrumentation, JMX, effective and stable debugging and
deployment, clustering and load
Jess Holle wrote:
The main item you didn't mention is instrumentation/JMX. This is an
area that should not require any substantive rearchitecture and could
greatly benefit most users. I know JBoss has more JMX stuff, but having
the Tomcat end of things quite well instrumented in Tomcat
more support in the
management/instrumentation/clustering and deployment areas I'd be a
happy chappy.
Allistair.
-Original Message-
From: Jess Holle [mailto:[EMAIL PROTECTED]
Sent: 22 December 2005 16:08
To: Tomcat Developers List
Subject: Re: Tomcat 6 plans (JSP 2.1)
Remy Maucherat wrote
:[EMAIL PROTECTED]
Sent: 22 December 2005 16:08
To: Tomcat Developers List
Subject: Re: Tomcat 6 plans (JSP 2.1)
Remy Maucherat wrote:
I don't see a big difference with Tomcat, which is also an appserver
(hopefully, you don't associate EJB - appserver, because if you do,
I'm not talking to you
Henri Gomez wrote:
Well memory is not the only point, faster start and less class to be
loaded is also very important for me. In my company we're still using
Tomcat 3.3.2 on our production servers (iSeries) since they are quite
fast to start and that's very important when you have at the same
2005/12/22, Remy Maucherat [EMAIL PROTECTED]:
Henri Gomez wrote:
Well memory is not the only point, faster start and less class to be
loaded is also very important for me. In my company we're still using
Tomcat 3.3.2 on our production servers (iSeries) since they are quite
fast to start
On 12/22/05, Remy Maucherat [EMAIL PROTECTED] wrote:
Henri Gomez wrote:
Well memory is not the only point, faster start and less class to be
loaded is also very important for me. In my company we're still using
Tomcat 3.3.2 on our production servers (iSeries) since they are quite
fast to
I didn't do any real benchmark, but the single-jar 5.5 should be as
fast on startup as 3.3.
good
Less class loaded - and less classes/features you need to worry when
setting up and maintainig is what I meant by footprint - Jetty is
around 0.5M I think.
what's the expected class/size for
On 12/22/05, Remy Maucherat [EMAIL PROTECTED] wrote:
Costin Manolache wrote:
I understand this doesn't help for JBoss - but tomcat != jboss.
I don't see the need for refactorings, and that's my *personal* opinion.
That's my opinion as well - if by refactoring you mean major code changes.
On 12/22/05, Henri Gomez [EMAIL PROTECTED] wrote:
Less class loaded - and less classes/features you need to worry when
setting up and maintainig is what I meant by footprint - Jetty is
around 0.5M I think.
what's the expected class/size for this SmallCat single jar ?
Around 1.4M without
For Servlet 2.5, the highlights are:
Requires 1.5 as minimum Java version.
Needs to support Annotations (probably the biggest project).
Some minor changes to Sessions to support Portlets.
A couple of really minor changes to 'web.xml' parsing.
Of course, you can always grab the spec as
Henri Gomez [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
2005/12/21, Bill Barker [EMAIL PROTECTED]:
For Servlet 2.5, the highlights are:
Requires 1.5 as minimum Java version.
Needs to support Annotations (probably the biggest project).
Some minor changes to Sessions to
Sorry, so far nobody has had the sense to propose returning to the good old
TC 3.3 Interceptors ;-). It looks like Evolution is here to stay.
I don't know if Interceptors would be a good solutions but I'd really
like to have something similar to Apache modules.
I would really like to have something more modular too - I understand
that NIO and the
other connector stuff is unlikely to see the main branch, but I think
'minimal standalone + modules' deserves a chance.
Even if we continue to ship by default a bloated tomcat, with all the
features anyone can
+1 to Costin's stuff... I've been itching for a truly minimal Tomcat
distro for a while...
Yoav
On 12/21/05, Costin Manolache [EMAIL PROTECTED] wrote:
I would really like to have something more modular too - I understand
that NIO and the
other connector stuff is unlikely to see the main
- What could prevent TC 6.x to became more modular ?
- Design, commercial dependencies or personal decisions.
Why not send a sort of vote on some possible architectures and plans ?
2005/12/21, Yoav Shapira [EMAIL PROTECTED]:
+1 to Costin's stuff... I've been itching for a truly minimal Tomcat
Well, it's not about 'vote' or plans, it's more about what people have
time to do.
I have checked in the build files for a 'standalone' tomcat in the
sandbox, I've been using the single jar almost exclusively, seems to
work fine. But I have a feeling I'm the only one interested in this
:-).
I'm willing to help...
Yoav
On 12/21/05, Costin Manolache [EMAIL PROTECTED] wrote:
Well, it's not about 'vote' or plans, it's more about what people have
time to do.
I have checked in the build files for a 'standalone' tomcat in the
sandbox, I've been using the single jar almost
Hi,
Besides adding support for Servlet 2.5 which does not seem too
overwhelming, most of the specification work is on support of JSP 2.1. I
am happy to report that Jacob Hookom is willing to contribute code to
add the necessary JSP support in Tomcat (he has done such an
implementation
+1
Costin
On 12/20/05, Remy Maucherat [EMAIL PROTECTED] wrote:
Hi,
Besides adding support for Servlet 2.5 which does not seem too
overwhelming, most of the specification work is on support of JSP 2.1. I
am happy to report that Jacob Hookom is willing to contribute code to
add the
-Original Message-
From: Remy Maucherat [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 20, 2005 12:32 PM
To: dev@tomcat.apache.org
Subject: Tomcat 6 plans (JSP 2.1)
Hi,
Besides adding support for Servlet 2.5 which does not seem too
overwhelming, most
There was some talk of merging the modules in 6, is there any objection
to that?
Keith
Bill Barker wrote:
I agree that the changes for Servlet 2.5 aren't that bad, but we might as
well branch Container while we are at it.
Hi,
Replying to three messages n one: see inline.
Besides adding support for Servlet 2.5 which does not seem too
overwhelming, most of the specification work is on support of JSP 2.1.
My observation as well.
am happy to report that Jacob Hookom is willing to contribute code to
add the
plans (JSP 2.1)
Hi,
Besides adding support for Servlet 2.5 which does not seem too
overwhelming, most of the specification work is on support of
JSP 2.1. I
am happy to report that Jacob Hookom is willing to contribute code to
add the necessary JSP support in Tomcat (he has
27 matches
Mail list logo
