At 09:42 2/28/2007, you wrote:
Back to the original issue: sounds like you really need to develop your own connector to handle your proprietary protocol, rather than trying to twist one of Tomcat's HTTP or AJP connectors into doing your bidding.
What we do is to be determined. What I want to do is sus out the *full*extent* of tomcat's capabilities so I know what I have to work with. We will build the (internal) sockets based protocol to optimize the abilities of what we have available :)
I am interested in what you mean by "connector" by that do you mean an interface to route connections to a Tomcat managed application that will work in concert with it's thread pooling etc? Is their a special more controllable API that such connectors use to dispatch requests to servlets?
Since I am working on an internal protocol in an enviroment where we also wish to use full HTTP1.1 for other URLs and interfaces into the same application(s), all the HTTP features are desired. The servlet development model, and the vast infrastructure it now is a part of, Deployers, IDE plugins, connectors, books, documentation, system loggers and monitors, developer administration, and people who know how to use all of it and other positive attributes are really fantastic assets, so we wish to leverage it as much as we can and not re-invent wheels.
I will put whatever HTTP headers are required to make tomcat operate (seeking minimum compliment) but after the connection is made and routed to the proper servlet I want to drop back to a binary non-http protocol for the duration of the connection. And if possible it would improve our system architecture If I could respond to the client without having to manage a lot of session state before all the input is read (actually, before all of it is written by the client to its outgoing socket) and processed. but at least so far with reading and testing it seems the input side of the socket is killed before or when one starts writing output. If this can be controlled by HTTP headers, tomcat config, setting something in an object etc then this would be a way we could do it and I'm very VERY interested in the possibility. We have full control of the client that will be connecting directly to tomcat "worker" instances.
PK --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
