tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <>
Subject Re: webapps and TCP/UDP listening sockets
Date Fri, 01 Jul 2011 02:07:55 GMT
Hash: SHA1


On 6/30/2011 7:14 PM, Tim Judd wrote:
> If I develop a webapp that listens for TCP/UDP sockets, which machine is 
> actually listening?

When you say "machine"... you mean ... what, exactly?

If you develop a webapp that listens for TCP/UDP sockets, where is the
socket bind occurring? If it's your webapp, then it really has nothing
to do with Tomcat at all: it's just like writing a non-webapp program
that binds to a socket and listens.

If you want to delegate incoming requests to threads from Tomcat's
request processor pool, that might be a bit tricky. Is that what you'd
like to do?

Do you really need Tomcat in this situation?

> Is the tomcat server listening (because the webapp is 
> running on that tomcat) or is the client listening (because he is running the 
> webapp on the tomcat server)!

Probably both, but it depends on your answer to the above questions.

> My goal is to have:
>   single UDP listening at tomcat server for packets, and
>   multicast UDP listening at the clients that is getting resended off the single 
> above UDP port from the webapp tomcat server

Why do you want to build this as a web-based application if HTTP isn't
really involved?

- -chris
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla -


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message