[vlc-devel] vlc plugin and attachment:// URIs

[Michael A. Puls II]

On Mon, 20 Jul 2009 16:29:15 -0400, Rémi <Denis-Courmont"  
<remi at remlab.net>> wrote:

> Le lundi 20 juillet 2009 23:21:29 Michael A. Puls II, vous avez écrit :
>> O.K. In this case, one just makes sure that they don't specify @data and
>> just stick to specifying an mrl param.
>
> I don't understand what you mean.

I'm saying as long as one sticks to:

<object type="application/x-vlc-plugin">
<param name="mrl" value="uri">
<param name="version" value="VideoLAN.VLCPlugin.2">
</object>

and doesn't use:

<object type="application/x-vlc-plugin" data="uri">
<param name="mrl" value="uri">
<param name="version" value="VideoLAN.VLCPlugin.2">
</object>

or

<object type="application/x-vlc-plugin" data="uri">
<param name="version" value="VideoLAN.VLCPlugin.2">
</object>

, then there will be no browser stream to worry about.

So, even though the standard way of loading a plug-in is to use @data, in  
the vlc plugin's case, you just don't and you won't have any problem.

>> However, with the attachment:// situation in Opera, do you think the
>> browser's streaming would be flexible enough there (since the data
>> wouldn't be coming over HTTP)? Or, do you think it'd be just as  
>> inflexible?
>>
>> If so, what about for now, make it so that if after:
>>
>>
>>   if( psz_target )
>> {
>>   // get absolute URL from src
>> char *psz_absurl = getAbsoluteURL(psz_target);
>> psz_target = psz_absurl ? psz_absurl : strdup(psz_target);
>>   }
>>
>> psz_target still starts with "attachment:", make the video area say "URI
>> scheme not supported"?
>>
>> Would that be acceptable?
>
> If it is attachment:// it could be dealt with a patch.

Do you personally know how to have the plug-in request the stream from the  
browser in this case?

> If it's attachment:/ as you said earlier, it's plain broken.

Why would "attachment://" be any easier than "attachment:/" to tell that  
you have an attachment URI?

psz_baseURL could be converted from "attachment:/..." to  
"attachment://..." if possible, I would think.

Thanks

-- 
Michael