Actually yes I did read the last e-mail.
This is how the matter is without turning compression off.
I saw that turning off compression was recommended, but I did not want
to tell all the developers to turn it off just yet since none of them
have reported this error occurring again.
I have told developers to increase their http-timeout value. If they
experience the problem again I then plan to have them turn the
http-compression off.
Maybe I am wrong, but I thought it was best to not turn
http-compression off unless necessary.
What are the disadvantages to turning http-compression off?
Is this only advised for those performing large commits, or is it a
general advisement for every subversion client user regardless if they
perform large commits or not?
I was just not comfortable turning this off until the large increased
http-timeout value proved to not help the issue.
Am I just be paranoid for no good reason?
-RG
On Thursday, Jul 17, 2003, at 10:19 America/Chicago, Ben
Collins-Sussman wrote:
> Russell Glaue <rglaue@cait.org> writes:
>
>> Concerning this issue. This is an update.
>> One of our developers set his http-timeout value really high, past
>> 600, to 720.
>> Since he set his client http-timeout value to 720, commits up to
>> almost 100 files at a time have not been failing. He has not yet tried
>> larger commits like before when this failed for us.
>>
>> I will post more updates if any new/different experiences develop.
>>
>> We are currently using Subversion 0.24.2
>
> Russell, have you not read my latest mail about timeout problems?
>
> We know the problem and the workaround now. Read this mail:
>
> http://www.contactor.se/~dast/svn/archive-2003-07/0964.shtml
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 17 18:35:18 2003