[vlc-devel] Re: [RFC] sanitize MRL format

[Damien Fouilleul]

Christophe Mutricy wrote:
>> Still, I would say that the "cleanest" solution would to enforce that 
>> the colon always be followed by two (or more) slashes, otherwise it 
>> will be considered part of the filename. That will break lame MRL such 
>> as udp:1.2.3.4 (but that's so inexcusably lame!)
>>     
> I'm in favor of that. A big fat warning should be printed when a demux:
> without // is detected and the behaviour changed in 0.9.1/0.10.0 
>
>   
>> Opinions, please.
>>     
> I don't know well src/input code. But i believe that in the demux case
> it tries first with the demux specified by the user/hinted by the access
> module, then try all the demux modules. Could we do the same for access
> modules ? It would solves the present problem and work for corner case
> like the http: directory.
>
>   
well, i've always been a pragmatic guy, i don't like restricting users 
more than it is strictly necessary. Regarding the MRL format, whether 
it's lame or not, i have no problem allowing format such as udp:1.2.3.4 
as long as the meaning is unambiguous, i mean firefox has no problem 
accepting file:c: and will dutifuly convert it as file:///c:/. Sometimes 
the 'right' URL format is more confusing than the lame version ;)

Anyway, i guess accepting 'lame' formats will complicate the URL parsing 
code, so, as everything, it's all about tradeoffs. But for my 2 cents 
worth, i'd like to see a first stage parser which detects malformed URL 
and try to convert them to the proper format, before passing it along to 
the rest of the chain, just like firefox do


-- 
This is the vlc-devel mailing-list, see http://www.videolan.org/vlc/
To unsubscribe, please read http://developers.videolan.org/lists.html