On Nov 24, 2005, at 7:10 PM, David Binger wrote:

> The durus client/server protocol is intended only for connection from
> a compliant durus client_storage:  all other connections are, for
> practical purposes, hostile.    This is good to know about, but I
> don't think
> there is anything here to fix.  If someone is sending non-compliant
> messages
> to the durus server, then shutting it down is reasonable.

Assuming that the durus port is not "maliciously accessible", then I
can very happily live with having durus shut down. I guess this is by
and large always the case. But what if durus server is running on a
different machine (anyone known to have done this?), then isn't there a
risk of having it maliciously shut down? No idea what other db servers
do in similar case.

The other aspect of this issue is that qp keeps forever (but maybe I
did not wait long enough) trying to send a request to the durus server
that is down... shouldn't this timeout? Or maybe restart the server?

mario