On 06/23/2013 07:47 PM, Greg Stein wrote:
> On Sun, Jun 23, 2013 at 3:56 PM, Blair Zajac <blair_at_orcaware.com> wrote:
>> On 6/22/13 1:22 AM, Lieven Govaerts wrote:
>>> Even better if we could cache this info somewhere automatically. So
>>> that the first time svn connects to a server ever it will use this
>>> 'slow' procedure, and then persists the results http/1.0 vs http/1.1
>>> and chunked-encoding supported somewhere. Like we already do for
>>> passwords and ssl certificate validation.
>> Will this work if you change where you are connecting from, e.g. at home one
>> day and then from a Starbucks or maybe your work where you have different
>> proxies in the path?
> Well... I don't think that we're talking (yet) about a cache. Just a
> config and an extra detection step. In your scenario, you'll suffer a
> slightly slower start cost (the extra OPTIONS), and in the other, a
> somewhat degraded experience (switching to C-L for all requests).
> But it should auto-switch as you move about.
> (assuming we don't try to cache, at this point)
Sounds good. Sounded like there was an idea of caching, which seemed
like it could be problematic.
Received on 2013-06-24 08:22:12 CEST