At 09:15 AM 10/11/2005 +0200, Tom wrote:
>On Thu, Oct 06, 2005 at 08:34:18PM -0600, Ken Kittlitz wrote:
> > Bug fixes, enhancements, etc. are most welcome!
>Why use HTTP, btw? Wouldn't TELNET make more sense? Or is there
>something I am missing?
Mostly because the web server (in this case, a servlet engine) can take
care of multiple incoming requests and the associated multi-threading
issues for us automatically. That's basically what the connection server
does now -- it acts as a "gatekeeper" to the database server, which only
accepts one connection and command at a time (as you discovered <g>). The
connection server has had its own bugs in the past, so if we can eliminate
it from the equation, so much the better.
Also, in theory at least, it should be easier to a deploy a servlet in
co-located server that supports Java but does not allow shell access. The
connection server is designed to run as a background process, which pretty
much requires access to a command shell to start it up.
Ken Kittlitz http://www.javien.com