This is an interesting proposition!  I read both of your posts.

Personally, if I were you, I would create a custom server.  David Flanagan's
Generic Multithreaded Server (as given in O'Reilly's Java Examples in a
Nutshell) would be a good starting point (if you're using it commercially,
there's a $50 license fee).

http://www.davidflanagan.com/javaexamples2/

I've never had Tomcat exhibit the request-killing behavior you describe.  I
have also never used a GenericServlet, so that could possibly be the cause.

-Jake

----- Original Message -----
From: "Wouter Bijlsma" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, March 21, 2003 2:01 PM
Subject: Connection drops with tomcat-based game server (very short version)


> Is it possible that tomcat sometimes randomly kills a request, does not
process a request or queues a request indefinitely, thereby blocking a
client that tries to read back the response to its request? Could this be
possible when a servlet communicates with the clients using only raw data
and InputStreams/OutputStreams? And: is it a good idea to develop a game
server for playing games like chess, chequers or draughts with tomcat,
considering the fact that tomcats main purpose is to act as web application
server using a strict request-response paradigm. Is it safe to assume that
every request made by a client always yields a proper response, also when
using raw data transfers? Also when there's a really high volume of requests
to a single servlet?
>
> Don't get me wrong: I do *not* think there's something wrong with tomcat!
As a matter of fact I have really good experiences with it using it for web
applications!!
>
> Kind Regards,
>
> Wouter Bijlsma,
> [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to