How to intercept request connections - custom connector?

[Darryl Pentz <dj...@yahoo.com>]

(This mail has been sent twice and been rejected by the Apache server as spam, but was sent from Nabble. Trying now from the actual mailbox. So apologies if this appears multiple times in the ml.)

I have 2 applications that run within a Tomcat 6 instance: 

1. a Grails web application 
2. a 'pure' Java server type application that exposes a web
services entrypoint as well as a regular Java socket that accepts
connections using our in-house proprietary protocol 

That second application with the regular socket is the problem
right now. The socket is obviously exposed on a different port to the port that
Tomcat is listening on. This requires our customers
to expose both 443 and 80 (which is what the regular socket listens
on). For reasons which you guys certainly won't want to know about, we
need to change this and run everything on *only* port 443. 

So my question is, is there any way to achieve this interception in Tomcat (perhaps by implementing a custom
connector?) that can 'peek' into the socket input stream when
the connection is made to Tomcat, and if it detects our in-house
protocol, to then divert that connection to our in-house handler, and
if not, then to let the regular Tomcat web server connector service the
request?

Thanks in advance, 
Darryl Pentz


      

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org