Simon Large wrote:
> Max Bowsher wrote:
>> Max Bowsher wrote:
>>> Simon Large wrote:
>>>> Max Bowsher wrote:
>>>>> Simon Large wrote:
>>>>>> With FSFS this is no longer true, certainly on Windows. You can
>>>>>> specify a UNC path to another machine in the form:
>>>>> Eek. I'm pretty certain that that is a fluke in the way the code
>>>>> came together, not a deliberate design decision of any kind
>>>> Well I asked the question about how to access UNC paths on the list
>>>> (which one - can't remember) and that was the answer that came back.
>>>> No-one contradicted it at the time. What is the official way of
>>>> accessing a UNC share, or are they unsupported?
>>> I do not know of any official or generally accepted unofficial method
>>> for representing an UNC path in an URL.
>>> Thus, I believe the answer is 'unsupported'.
>> I've just googled my way to an official IETF internet draft, proposing
>> file:////servername/path. And, just for contrast, Mozilla currently
>> works with file://///servername/path. So, in summary, there is no
>> standard way to access an UNC path through an URL yet, but if the
>> IETF declares a standard, Subversion will likely support it.
> OK, but does that mean that the file:///\ method may disappear at some
> random time? Some Windows users are already using it. FWIW, TSVN
> (currently) supports file:///\ and file://///, the latter being
> internally converted to the former.
> I see this was discussed again last October, but not resolved:
> I agree that the unsupported file:///\ method is ugly and looks wrong,
> but with no fix in sight, the number of users taking it up anyway will
Could you file an issue, please, describing the situation?
I think that if we have a record that file:///\ is in use, then we will
preserve it so long as that does not conflict with any other use.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Apr 22 11:04:47 2005