Fwd: Re: how to enable Tomcat to handle proprietary TCP streams (non-http data)

2010-12-09 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 All, Oops... I managed to send this to the OP and not to the list. - -chris - Original Message Subject: Re: how to enable Tomcat to handle proprietary TCP streams (non-http data) Date: Wed, 08 Dec 2010 15:04:40 -0500 From

Re: how to enable Tomcat to handle proprietary TCP streams (non-http data)

2010-12-09 Thread Peter Crowther
On 8 December 2010 19:51, razor wrote: > So i can just start my own thread (threads) for receiving non-http > data (where to put initialization/starting stuff? as a new servlet ? ) > If you implement your entire non-HTTP system as a servlet in its own context, you have the advantage that you c

Re: how to enable Tomcat to handle proprietary TCP streams (non-http data)

2010-12-08 Thread razor
So i can just start my own thread (threads) for receiving non-http data (where to put initialization/starting stuff? as a new servlet ? ) and then my code will put received data in some 'public' synchronized queue/collection or database (like HSQLDB) and other threads/modules (and again, where

Re: how to enable Tomcat to handle proprietary TCP streams (non-http data)

2010-12-08 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Łukasz, On 12/8/2010 2:23 PM, Łukasz Tołwiński wrote: > I'm not sure how to reply to mailing list (am I replying to you or > tomcat.users ? ) You succeeded in replying to me, but it's more appropriate to reply to the list. > I'm still wondering what

Re: how to enable Tomcat to handle proprietary TCP streams (non-http data)

2010-12-08 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Razor, On 12/8/2010 7:15 AM, razor wrote: > I'm writing application composed from few loosely coupled components > (dependency > injection pattern, all compoments written by my team). First of them listens > for connections, spawns new thread (server