Bill Barker wrote:
AFAICT, this code is assuming that there will always be a message body in
the POST Request. However, this is not necessarily the case (and is
certainly not true for the problem at hand). Eventually,
SocketInputStream.read() is called from within
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
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 balancing are the types of areas that
would help me out
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
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=38010.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
On Dec 22, 2005, at 4:52 AM, Remy Maucherat wrote:
Bill Barker wrote:
AFAICT, this code is assuming that there will always be a
message body in the POST Request. However, this is not
necessarily the case (and is certainly not true for the problem
at hand). Eventually,
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
Je serai absent(e) du 22/12/2005 au 02/01/2006.
I will be out of the office untilJanuary the 2d.
Please contact [EMAIL PROTECTED] or call DMT Customer Service 0033 479 264
723
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Personally I am a fan of the light-weight approach. Using Tomcat but
adding enterprise value at webapp level with Spring and Hibernate has
been a fantastic combination for us. I've not delved into EJB3 much but
I hear it's just POJO CMP stuff which Hibernate does.
If Tomcat could just provide
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=38011.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
The @Resource is a biggy with the JEE 5 within the Servlet Container.
There are some deficiencies with the spec such that there was no Class/Factory
support for these fundamental annotations, so now supplemental frameworks that
have reliance on injection (JSF for one) becomes container specific
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
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=38012.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=38012.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=38012.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Bill Stoddard wrote:
Nope, that's incorrect.
From RFC2616, the official HTTP standard definition:
The presence of a message-body in a request is signaled by the
inclusion of a Content-Length or Transfer-Encoding header field in
the request's message-headers.
A bodyless POST request
Remy Maucherat wrote:
Bill Stoddard wrote:
Nope, that's incorrect.
From RFC2616, the official HTTP standard definition:
The presence of a message-body in a request is signaled by the
inclusion of a Content-Length or Transfer-Encoding header field in
the request's message-headers.
A
Remy Maucherat [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Bill Barker wrote:
Tomcat handles it much the same way for for a 404 ;-).
However, I'm guessing that Httpd sets up an EOS-only bucket-brigade (but
am not interested enough to look it up :), so that if the target
24 matches
Mail list logo