Thanks very much!
The big hope is all the socket connection and thread pool management
"wheel re-inventing" etc is "done" and I can do it mostly "high
level" except for the interpreting of the input protocol byte
streams. Have it do somehing like:
ProtocolConnectorThread.onListenerConnect(i
"Peter Kennard" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> would definately be someting to do.
> one has to wade through a lot of stuff to get to that point :)
> I have to find out where what defines a connector is, how it is installed
> and configured ...
>
Well, the first t
would definately be someting to do.
one has to wade through a lot of stuff to get to that point :)
I have to find out where what defines a connector is, how it is
installed and configured ...
So what people are saying is "get the source and build it" as step #1 ??
At 16:38 3/2/2007, you wrote:
On 3/2/07, Peter Kennard <[EMAIL PROTECTED]> wrote:
What I would like to do is take an AJP connector,
redo it's insides to parse another format and
then pass the requests off to servlets.
Seems to me that looking at the differences in source between two
connectors (e.g. AJP and HTTP) would be
I think the existing connectors in tomcat source could be the only
existing documentation :)
Not a good sign for them being "officially" supported.
Has anyone here made one?
What I would like to do is take an AJP connector,
redo it's insides to parse another format and
then pass the request
Peter Kennard a écrit :
> I want to write my own "protocol handler" which I can configure as a
> connector. I want it to do something along the lines of AJP - packet
> hits in, servlet hits out.
>
> B - I want a good reference on what class I need to subclass, how to
> use it and what are consi
I want to write my own "protocol handler" which I can configure as a
connector. I want it to do something along the lines of AJP - packet
hits in, servlet hits out.
A - should I be posting this to a "dev" list?
B - I want a good reference on what class I need to subclass, how to
use