Re: [Tclhttpd-users] Re: multiple clients

[Colin M. <co...@fi...>]

> 3) If the server blocks for some other reason it can indeed starve clients.
> The most typical example is if you make SQL calls to a database server directly
> from TclHttpd.  Those calls will block until the SQL server returns the answer.
> Right now the OraTcl and SybTcl interfaces do not really support a non-blocking
> interface that will free up TclHttpd to get back into its event loop.

I've got a postgresql tcl interface which doesn't block on the db server backend, so 3 doesn't necessarily apply.

You can have it if you want, it's GPL :)

Colin.