On 4/3/06, Leon Rosenberg <[EMAIL PROTECTED]> wrote: > Why then using tomcat at all? What's wrong with writing own app, which > listens on a socket and does whatever it has to do? Before you have to > rape tomcat to perform a task it was never designed for...
Yes, indeed. In many cases, it would seem all you want to do is layer some sort of custom protocol over HTTP (= use a fake HTTP request to establish the connection, and then do whatever you want; since there's control over the client and the server, parsing the HTTP artifacts will not be a problem). Tomcat (or any other high level container), the Servlet API, and maybe HTTP itself could get in the way of such usage, and a simple low level solution could be better. -- xxxxxxxxxxxxxxxxxxxxxxxxx Rémy Maucherat Developer & Consultant JBoss Inc xxxxxxxxxxxxxxxxxxxxxxxxx --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
