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 an object that extended a core tomcat 4 class, HttpBaseRequest.
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 has a bunch of set methods.
presumably, any container in which the ajp connector is being used will
already have some request object with a bunch of set methods, so the
interface approach is probably less work. however, the concrete object
approach is probably more efficient, as it's probably easier to delay
conversion from bytes to strings in this case.
anyway, i'm not really sure what the best approach is -- that's why it's
a dilemma :) -- so, i'm looking for opinions, suggestions, etc. here.
-kevin.
