db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmars...@Sourcery.Org>
Subject Re: [VOTE RESULT] Re: Help detecting client disconnects for network server
Date Sat, 16 Oct 2004 00:07:24 GMT
Hash: SHA1

Kathey Marsden wrote:
> Samuel Andrew McIntyre wrote:
>>>So, I'm still not sure that I like having keepalive set by default
>>>without a way to turn it off.
> OK, so, given the input from everyone I submit the following solution to
> vote:
> 1) Have keepAlive on by default. It seems important not only for locks
> but for potential network server bloat due to connections not getting
> cleaned up.
3 +1's
> 2) Add a property derby.drda.keepAlive={true|false} (defaults to true as
> described above).  There seems to be a need to be able to turn keepAlive
> off in some cases.
2  +1's  and a strong argument for it without an actual vote.

We didn't hear any arguments to Dan's last question about why we
shouldn't have an option to turn keepalive off.  So, unless anyone posts
 any objections, I will submit 1 and 2 on  Monday.

> 3) Add property derby.drda.connSoTimeout=<milliseconds> (defaults to 0,
> infinite) to provide the ability to have connections timeout after a
> period of inactivity. The connections will still timeout, even if the
> connection is working fine but will timeout after blocking on a read for
> this length of time.   I am about +.5 on this one.  It would be nice to
> provide the capability, but hesitate to add yet another property.
Haven't seen a consensus for #3 so will just abandon this vote.
An option was proposed for an embedded option which would only timeout
the connection if it is holding locks.  Anyone interested in this or
other options can pursue it on another thread.  I won't go down that
path as it is unlikely  I would implement something like that myself.



Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org


View raw message