db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmars...@Sourcery.Org>
Subject [VOTE] Re: Help detecting client disconnects for network server
Date Mon, 11 Oct 2004 17:43:46 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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.
	

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.
	

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.



Kathey



	




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

iD8DBQFBasIbG0h36bFmkocRAuGIAJ4138QyCiQfPUYi9huGSva/wrnaqwCgi4lL
usc5GVA4F8NSioDH1a+qf+I=
=w+tm
-----END PGP SIGNATURE-----

Mime
View raw message