...created a separate class (possibly a separate application) to do work on other ports and protocols and have a servlet that can talk to that other class when needed...
Bill
Thx Bill for the answer. Did I get it right:
- I create a standalone
Java app that handles my port xyz and then talks to the servlet or the servlet talks to it. For the later a subscriber
pattern seems appropriate?
To twist the question a bit: If the servlet can listen on port 80 (or 443), but the "talk" coming in is not http but the protocol/syntax used by a CVS client. Would that be a feasible use for an servlet?
Thx