The problem is not only the Request object, but the whole
infrastructure
needed for efficient communication ( MessageBytes, Headers, etc ).
i've started down this path (1). there's a bunch of stuff in tomcat 3
(like MessageBytes) that would be useful... i posted a
message a couple
days
i actually decided to copy a bunch of low-level utility classes from tc
3 to jtc/util until something like a jakarta-tomcat-commons exists...
GOMEZ Henri wrote:
The problem is not only the Request object, but the whole
infrastructure
needed for efficient communication ( MessageBytes,
so, i'm looking at decoupling the Ajp13 java stuff from servlet
container code.
some background... in tomcat 3, the ajp code takes a core
tomcat Request
object and adds decoded information from the ajp request into the
Request object. when i ported this code from tomcat 3 to tomcat 4, i
used
On Mon, 14 May 2001, kevin seguin wrote:
so, i'm looking at decoupling the Ajp13 java stuff from servlet
container code.
some background... in tomcat 3, the ajp code takes a core tomcat Request
object and adds decoded information from the ajp request into the
Request object. when i
the dilemma is what to pass to the ajp code that accepts requests in the
new world where this code could be used by any servlet container. the
choices as i see them are:
1) a concrete object (say AjpRequest) that takes and stores information
from the request
2) an interface that
so, i'm looking at decoupling the Ajp13 java stuff from servlet
container code.
some background... in tomcat 3, the ajp code takes a core tomcat Request
object and adds decoded information from the ajp request into the
Request object. when i ported this code from tomcat 3 to tomcat 4, i
used
