Re: supporting http proxy via a config file

Karl Fogel <kfogel@newton.ch.collab.net> writes:

> Philip Martin <philip@codematters.co.uk> writes:
> > Using separate files also allows the information to be shared by
> > different programs. There is no reason why the proxy setup, say,
> > should be restricted to just Subversion. This may be what Greg was
> > alluding to with his ./configure/proxies suggestion, i.e. it is not a
> > Subversion specific file and may be read by other apps.
>
> If the file is in ~/.subversion/, and its syntax is defined by the
> Subversion developers, then the app has to learn where and how to read
> it.
>
> Given that, wouldn't readability by other apps be as possible for a
> single big file as for smaller, domain-specific files... (?)

A non-Subversion app will in general only want a small part of the
Subversion config. Maintaining a "proxies-only" parser should be
simpler than a "complete-subversion" parser. This assumes the
non-Subversion app is using its own code, if it can use the Subversion
libraries to handle the files the problem doesn't occur. Not all
applications will want/be able to use the Subversion libraries.

-- 
Philip
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org