I did see a reference to a "socket servlet" which touches on this.
Tomcat has doe a lot in it that is very useful (to re-itterate)
- Administration of sevlets on a "live" server with web interface
- handling of depolyment and undeplyment
- integration with IDEs and build systems (eclipse, ant, etc)
(I could go on but it is a tested reliable system with a lot of goodies)
We have an internal non-http messaging system gateway which routes
blocks of low latency messages to applications. I would like to use
Tomcat as an "application module manager" for this system. The
applications in most cases desire to act as proxys between the
internal messaging system and the HTTP web world for web clients so
the all the HTTP goodies like apache connectors are highly
desired. I am working on determining the feasbility of using tomcat
for this purpose.
Some questions :)
- What is the absolutely minimal HTTP header required to cause tomcat
to invoke a servelet for processing binary content? ie: "POST HTTP
1.0 ... " ??
- Is there a way to create a servlet to serve some other protocol
(lowest level, lowest overhead) than an HTTP request?
- Is there a way to have a servlet serve a persistent connection
(like a telnet terminal session)
- If the "default" servlet process a request and uses a field as
routing information to another servlet is there any significant
overhead in forwarding the request to another servlet.
I know I'm stretching it a bit but this would be really useful!!
Thanks!
Peter K.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
