/el-niño.jsp should be sent (per the w3c recommendation) as
/el-nin%c3%b1o.jsp which is a UTF-8 encoded bytes sequences for any
characters which aren't in the ~60 characters allowed from ASCII. The
encoding used for the byte conversion is not specified in the official
URI spec (RFC 2396), but the
> This hack definitely works. As long as you're willing to pay the overhead
> for the method call, it's essentially equivalent to asking Log4J whether
> or not debugging output is enabled, which does something similar (but asks
> the instantiated logger object, instead of being a static method).
Actually I've got a thought on how to add in debug messages without recompiling. For
a horrible hack say I've got a java class
like:
//Constants.java
public class Constants{
public static boolean isDebug(){return true;}
}
And in my main code I call:
if(Constants.isDebug()) log(someNastyFun
Jakarta-tomcat-connectors appears to be available only through CVS. The src can't be
obtained from http://jakarta.apache.org/ I
was wondering about the connectors myself until I went to the CVS repository directly.
Would it not make sense to bundle the j-t-c code into a tar ball for those who
Mandrake 5, Redhat 6.2, Redhat 6.2 Enterprise, Redhat 7.0, Redhat 7.1 (with all the
compat libs) under variation of IBM1.3, Sun1.3,
Sun1.3.1
Window 2000 (SP2) and Windows NT 4 (Service Pack 6)
