[FFmpeg-devel] [RFC] Browser remote content API

[Lukasz Marek]

On 10.02.2014 03:29, Michael Niedermayer wrote:
>>> > >also i would suggest you design and implement the API without the
>>> > >student to not complicate that further
>> >
>> >Not sure I understand.
>> >You want a student to implement this at protocol level only (new
>> >callback) and lavf would be prepared before?
> it will take you less time to design and add the framework/API
> without a student than with.
> so why do it with one ?
>
> you know ffmpeg and the API, the student doesnt
>
>

I've attached implementation of my proposal API.

Second patch is just for testing purposes, but probably may be helpful 
for the student. Example may be also merged at some point when first 
protocol supports it.

-- 
Best Regards,
Lukasz Marek

When you look long into an abyss, the abyss looks into you. - Friedrich 
Nietzsche
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-lavf-avio-add-directory-list-API.patch
Type: text/x-patch
Size: 6125 bytes
Desc: not available
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20140216/c0c2c454/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-fake-implementation-of-list-dir-API-and-test-program.patch
Type: text/x-patch
Size: 5184 bytes
Desc: not available
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20140216/c0c2c454/attachment-0001.bin>