[webkit-dev] Feature announcement: Web VHS API

[Ryosuke Niwa]

Why are rewind(), forward(), pause() and eject() all blocking APIs? I don't
think we should be blocking the main thread while those operations are
taking place.  In particular, rewind() can take anywhere from a few seconds
to a few minutes.  We should let authors show some kind of UI for
rewinding, and keep the web page responsive while VHS is rewinded.

I'm also confused by the fact VHSOutput interface has a
method, streamToYouTube, that specifically supports one website.  Are we
expecting to add methods like streamToDailyMotion, streamToUStream, etc...?
 I'd prefer coming up with a generic format and let author specify an URL
to which the video is streamed.

Also, why are VHSInput and VHSOutput separate interfaces?  It appears that
all methods on those two interfaces can just be on VHSAccess.

- R. Niwa


On Mon, Apr 1, 2013 at 4:17 AM, Alexis Menard <alexis at webkit.org> wrote:

> Hello,
>
> I would like to let you know that I plan to add support for the Web VHS
> API to WebCore. The Web VHS API is a specification to bring VHS support to
> the Web.
>
> This support will be behind the ENABLE_WEB_VHS feature define.
>
> The spec is here:
> http://bit.ly/YVHIga
>
> Here is the tracking bug:
> https://bugs.webkit.org/show_bug.cgi?id=113697
>
> Let me know if you have any questions or comments.
>
> Best regards,
> Alexis
>
> --
> Software Engineer @
> Intel Open Source Technology Center
>
> _______________________________________________
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20130401/e589267f/attachment.html>