At 04:43 AM 2/19/2005, Remy Maucherat wrote:
William A. Rowe, Jr. wrote:
It definately seems like j-t-c should be a first candidate
for svn conversion. The other jakarta-tomcat repositories
are considerabily more complex.
But it would be good to have line endings straightened out
beforehand.
I
William A. Rowe, Jr. wrote:
It definately seems like j-t-c should be a first candidate
for svn conversion. The other jakarta-tomcat repositories
are considerabily more complex.
But it would be good to have line endings straightened out
beforehand.
I find svn quite confusing to work with.
So I don't see the point of forking 1.3. Both config and core features
are the same. Of course some advanced configuration properties where
changes, lot new added, but from the outside its still old mod_jk.
OK, understood from below. I agree concerning JNI deprecation. But read
comments about
Rainer Jung wrote:
With stickyness and session id one would have:
- sticky worker (the correct one)
- failover for the preferred (your redirect)
- any other in the same replication cluster (domain)
- the rest (loose session but can start the app again from the beginning)
Your redirect concept and
At 12:56 PM 2/17/2005, Rainer Jung wrote:
Hi,
first: thanks a lot to Mladen for adding all the beautiful features [and
removing CRLF :) ]. Big leap forward!
Here's a list of all mixed up line endings currently
in jakarta-tomcat-connectors/jk/ ...
The Mismatch'ed files all represent files with
William A. Rowe, Jr. wrote:
Here's a list of all mixed up line endings currently
in jakarta-tomcat-connectors/jk/ ...
The Mismatch'ed files all represent files with mixed line endings
(some cr/lf, some cr/cr/lf.)
Two things.
See no CRLFs for any .h or .c inisde j-t-c.
Also Bill, will you be OK
It definately seems like j-t-c should be a first candidate
for svn conversion. The other jakarta-tomcat repositories
are considerabily more complex.
But it would be good to have line endings straightened out
beforehand.
This checkout was with the cvs Win32 client. It seems, from
all the
William A. Rowe, Jr. wrote:
It definately seems like j-t-c should be a first candidate
for svn conversion. The other jakarta-tomcat repositories
are considerabily more complex.
Yes, if everyone else agree we should consider moving to svn.
The problem is only with Tomcat build process. If ant
Rainer Jung wrote:
Hi,
first: thanks a lot to Mladen for adding all the beautiful features [and
removing CRLF :) ]. Big leap forward!
Still, I cope with those on a daily basis.
I think that until Monday we were still in the progress of adding
features, and fixing bugs. 1.2.8 changed a lot
