jfclere 2002/06/23 08:54:13
Modified:jk/native2/common jk_msg_ajp.c
Log:
Replace the 4's by AJP_HEADER_LEN (Where they were header length).
Revision ChangesPath
1.18 +7 -7 jakarta-tomcat-connectors/jk/native2/common/jk_msg_ajp.c
Index: jk_msg_ajp.c
At first let me warn you. Normally I'm really bad at C programming.
I had some problems building and running mod_webapp (from CVS) with Apache
1.3 on my Debian box.
Getting a Segmentation Fault on every access to something mounted with
mod_webapp.
Finally I came up with the attached patch and
Nico Seessle [EMAIL PROTECTED] wrote:
At first let me warn you. Normally I'm really bad at C programming.
I had some problems building and running mod_webapp (from CVS) with Apache
1.3 on my Debian box.
Getting a Segmentation Fault on every access to something mounted with
mod_webapp.
pier2002/06/23 09:50:40
Modified:webapp/apache-1.3 mod_webapp.c
Log:
Fixed apr_psprintf - ap_psprintf for Apache 1.3. The pool used in
request_rec is not an APR memory pool...
PR: none
Obtained from:Tomcat Mailing List [EMAIL PROTECTED]
Submitted by:
nacho 2002/06/23 12:04:48
Modified:jk build.xml
Log:
Exclude more filetypes from copiying when building jk2 docs
Revision ChangesPath
1.44 +3 -0 jakarta-tomcat-connectors/jk/build.xml
Index: build.xml
Christopher K. St. John wrote:
Bill Barker wrote:
I agree with Remy
that any single benchmark suite isn't going to tell you how your particular
web-app will perform.
Bill,
Actually, I agree, but this isn't what that is :-)
There's a difference between:
a) Benchmarks for
Glenn Nielsen wrote:
-1 At this time for starting work on Tomcat 5 (jakarta-tomcat-5)
This is not a good time to start work on Tomcat 5 based on the
proposal as put forward for the following reasons:
1. There are alot of new features and changes in Tomcat 4.1.
These have not been
Pier Fumagalli wrote:
Remy Maucherat [EMAIL PROTECTED] wrote:
Pier Fumagalli wrote:
As far as I would like to see WARP and its future development, it'll
probably end up following a different container architecture. The
extenization of the HTTP stack from the core of the container brings some
remm2002/06/23 13:35:30
Modified:catalina/src/share/org/apache/catalina/startup
ContextConfig.java
Log:
- Don't remove resources on stop (only the resources specified in web.xml would
get added back).
Revision ChangesPath
1.66 +16 -4
Remy Maucherat [EMAIL PROTECTED] wrote:
Working as well as possible with Apache is my objective.
Providing a great Java web server is also my objective.
To some extents, these two objectives contradict each other. You can see
this already in the design of Catalina, and in the hacks that I had
On Sun, 23 Jun 2002, Pier Fumagalli wrote:
That would be a waste of time and CPU resources... You're looking in the
wrong direction... To get performance, and reliability, all you have to do
is simplify the code, removing layer after layer... Not adding them...
Have you read the proposal ?
Pier Fumagalli wrote:
Remy Maucherat [EMAIL PROTECTED] wrote:
Peace Pier. I think there's a misunderstanding ;-)
Working as well as possible with Apache is my objective.
Providing a great Java web server is also my objective.
To some extents, these two objectives contradict each other.
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Did you look at JK 2 at all ?
Yes, I did. And in my opinion, it sucks. But my spare cycles are limited to
:-)
Allways nice to hear an objective and argumented opinion from Pier.
Who can beat the Because I say so argument ?
Good... FWIW, you
Glenn Nielsen [EMAIL PROTECTED] wrote:
I think the current proposal is too vague. It needs to be broken out
into greater detail. You need to ask the tomcat developer community
what new features they think are needed, what code smells bad enough
to need refactoring, and what areas of Tomcat
On Sun, 23 Jun 2002, Glenn Nielsen wrote:
[snip]
Providing a great java web server is not a goal of Tomcat.
[snip]
I didn't know cats could talk :-).
I didn't know that Glenn, or Pier, or any single developer, speaks for the
entire Tomcat developer community.
This statement (a great
mturk 2002/06/22 22:40:29
Modified:jk/native/apache-2.0 mod_jk.c
Log:
Fixing the compile time warning:
'jk_apr_pool_cleanup' function must return a value
Revision ChangesPath
1.46 +2 -1 jakarta-tomcat-connectors/jk/native/apache-2.0/mod_jk.c
Index:
mturk 2002/06/22 23:55:56
Modified:jk/native2/common jk_channel_socket.c
Log:
Costin changed it to use read/write instead of send/receive.
Unfortunaly that doesn't work on WIN32 cause read/write cannot operate on sockets.
Perhaps we shoud reverse that unless there is a strong
Craig R. McClanahan [EMAIL PROTECTED] wrote:
On Sun, 23 Jun 2002, Glenn Nielsen wrote:
[snip]
Providing a great java web server is not a goal of Tomcat.
[snip]
I didn't know cats could talk :-).
I didn't know that Glenn, or Pier, or any single developer, speaks for the
entire
On Sun, Jun 23, 2002 at 06:23:04PM +0200, Nico Seessle wrote:
At first let me warn you. Normally I'm really bad at C programming.
I had some problems building and running mod_webapp (from CVS) with Apache
1.3 on my Debian box.
Getting a Segmentation Fault on every access to something
Albert Chin [EMAIL PROTECTED] wrote:
On Sun, Jun 23, 2002 at 06:23:04PM +0200, Nico Seessle wrote:
At first let me warn you. Normally I'm really bad at C programming.
I had some problems building and running mod_webapp (from CVS) with Apache
1.3 on my Debian box.
Getting a Segmentation
On Sun, 23 Jun 2002, Craig R. McClanahan wrote:
Tomcat can meet all of those needs, but only if the developers are
unselfish enough to understand that I don't need that feature does *not*
mean it should not be there at all. Such selfishness has not
+1
I think this should be somehow
JSPs don't seem to be setting the Content-Type header correctly. Have
attached a patch that adds the missing 'charset=' string to the
content-type value.
thx,
arvind
GET /foo.jsp HTTP/1.0
HTTP/1.1 200 OK
Content-Type: text/html;ISO-8859-1
Connection: close
Date: Mon, 24 Jun 2002 02:07:50 GMT
Good proposal goals provide a way to test if the goal
has been achieved and a way to argue if the goal is
worthwhile. Improve performance as a goal is both
untestable and impossible to argue with, so it's a
badly stated goal.
Remy Maucherat wrote:
To evaluate code, I strongly recommend
Hi,
There is one strange (well, not that at all) behavior of mod_jk2 that I
would like to fix.
When we load the module, the channels gets opened on the first client
request. Now, the problem lies in the fact that the next client can send
request prior the channel is opened, since opening takes
I thought the ASF was about creating a community (meritocracy) where
proposals, ideas, directions, and code can be discussed openly and the
validity of them could be challenged. So that only the best ideas rise
to the top. When did this get redefined to mean selfish?
I see the proposal
25 matches
Mail list logo
