W3C home > Mailing lists > Public > public-device-apis@w3.org > December 2009

Capture API and the duration argument

From: Paul, Andre <Andre.Paul@fokus.fraunhofer.de>
Date: Mon, 21 Dec 2009 12:38:26 +0100
Message-ID: <79C0EA6E7AD7CE4A85EDAF482B5456B20250FE6F@EXCHSRV.fokus.fraunhofer.de>
To: <public-device-apis@w3.org>
Hi all,


Just some quick questions to the proposed duration argument:


"duration double not nullable not optional Maxium duration of a single video clip in milliseconds."


The current proposal of the capture API is to use native applications for capturing media. The question is what should happen after the duration exceeds the given maximum value? Should the native client process be killed by the Web-runtime? How should the Web-runtime know the actual duration of a video clip (how long is the user looking to the live preview (viewfinder) and when was recording started by the user?). Or will the user record its video and afterwards the video is checked against the duration and dropped if it is to long?


Do you make mandatory requirements to native capturing applications to realize the duration attribute and what is the purpose of the duration attribute? Isn't it up to the user to decide how long a recorded media should be?


Btw: In terms of future backwards compatibility limit and duration should be encapsulated into an options object (as initially discussed in the mailing list)


Kind regards,




André Paul, Dipl.-Inform.                    

Future Applications and Media


Fraunhofer Institute for 

Open Communication Systems   


Kaiserin-Augusta-Allee 31      

D-10589 Berlin, Germany    


Email:  andre.paul@fokus.fraunhofer.de <mailto:andre.paul@fokus.fraunhofer.de> 

Tel:    +49-30-3463-7336



Received on Monday, 21 December 2009 11:39:02 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:41 UTC