"Tim O'Neil" <[EMAIL PROTECTED]> wrote:
>> Tomcat (or Apache, or any other TCP based server) sends responses back on
>> the same port that it received your request on (in fact, on the exact same
>> connection). Is your application itself generating outbound TCP
>> connections (for example, to connect to a database)? Or is the arbitrary
>> port possibly the one created by your *browser* running on the same
>> machine and connecting to Tomcat?
>
> Not true in some cases. HTTP sends its response info on the same port,
> protos like ftp open another port. (Which is the reason for http being
> a stateless protocol, you need to open a second port to do things like
> random stream access.)
Correct... Based on HTTP, for example, there's RTSP (Real Time Streaming
Protocol) which use a more-or-less stateless TCP connection for
"controlling" the other UDP-based streams carrying the actual data.
> But that his application is wanting to open another
> port has nothing to do with tomcat, or at least I doubt it. Is your app
> a CORBA or JNI app by chance Joe?
Joe's scenario looked a lot like a EbXML, RosettaNET, BizTalk or similar
transaction, where the "action" is decoupled from the request-response model
of the transport (HTTP in this case), as, as I told before, that might
involve long transaction processing, human intervention,
name-your-favourite...
Can be solved, though! :) java.net sucks but not THAT badly! :)
Pier
