[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[patch #4992] Client/Server connection timeout

From: Derek Robert Price
Subject: [patch #4992] Client/Server connection timeout
Date: Tue, 28 Mar 2006 13:04:38 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20060111 Firefox/

Follow-up Comment #3, patch #4992 (project cvs):

It's possible CVSLCKSLEEP + something bigger than 1 might make sense with a
heavily loaded server.  Perhaps with a commit, which I dare say might have to
wait for a lock, the check pass might run for longer than a second before
getting to the second (commit) pass and returning any data, causing an
undesirable timeout with this default.

Maybe CVSLCKSLEEP + 30 would be a more reasonable default?  It seems somewhat
reasonable to expect any user dealing with a server that would take longer
than 30 seconds to run the commit check pass to know they should lengthen the
timeout.  Anything longer seems unnecessary and tedious for the user (keeping
in mind that this will actually take a total of 60 seconds to timeout).

If we're wrong, it will be easy enough to fix after the first few bug


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]