Karl Fogel <kfogel@newton.ch.collab.net> writes:
> Garrett Rooney <rooneg@electricjellyfish.net> writes:
> > i seem to recall that in one of the discussions about ra_pipe, there
> > was some discussion about how to put this kind of data in the config
> > files. personally, i'd find it MUCH more convenient than an
> > environment variable. does anyone remember what the proposed syntax
> > for this sort of thing was?
>
> Config file should be supported as well as environment variable, but
> Greg's question is still relevant: what's the "bit" in the URL that
> says to use the tunnel? (And I do think we want that flexibility,
> i.e., the ability to tunnel or not tunnel by changing the URL).
Maybe there shouldn't be a bit in the URL that says to use the tunnel.
It seems wrong that different users would need to use different URL's
to refer to the same repository. Whether a tunnel is needed is a fact
about the user's local network configuration, not a fact about where
the repository is.
For example, Red Hat has offices in Toronto, ON and Mountain View, CA.
Each office has its own tunneling proxy the people working there
should use for HTTP requests to Red Hat internal web sites. And I
think people in the main office in North Carolina don't need any proxy
at all. But we still want to be able to trade URL's between the
Toronto, Sunnyvale and Centennial offices without thinking about each
other's proxies.
Our current arrangement allows just that. We have HTTP proxy
configuration files that say: "For requests to these hosts, use this
proxy; for http requests to those hosts, use that proxy; ...". The
right proxy configuration is a bit of local expertise that you get
from your officemates.
Isn't the instinct to mark up the URL with proxy flags a holdover from
CVSROOT?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Dec 4 20:45:41 2002