On Mon, Jul 27, 2015 at 7:31 PM, Ted Mielczarek <t...@mielczarek.org> wrote:
> On Fri, Jul 24, 2015, at 12:43 PM, Jonas Sicking wrote: > > On Fri, Jul 24, 2015 at 3:49 AM, David Rajchenbach-Teller > > <dtel...@mozilla.com> wrote: > > > On 24/07/15 11:38, Jonas Sicking wrote: > > >> I think we should allow addons to implement something like this. But I > > >> don't think it's something that we should let apps do. > > >> > > >> / Jonas > > > > > > So Dropbox, Cozy Cloud, etc. should be add-ons instead of apps? > > > > Yes. For FirefoxOS we're working on getting rid of installation for > > "apps". Instead apps will be treated just like other web content that > > you simply browse to. > > > > In this model it doesn't make as much sense for apps to be changing > > the behavior of the user agent. Why would navigating to Dropbox and > > then navigating away from it suddenly change the behavior of your OS? > > How do you revert it? > > > > Instead we're going to use addons as the way that you customize your > > device. > > I've been actually thinking about this exact use case recently (storage > providers) and I think it would behoove us to figure out how to make > this work for webapps. If you require addons to make this work then > every storage provider needs to write addons for every browser, which > means that they're likely to just not have support for Firefox OS. If > you make this a web app feature instead, then providers can simply use > the web API and any user agent that supports it will get support, > meaning that Firefox OS is likely to be supported. > This is pretty similar in spirit to the existing > navigator.registerProtocolHandler, although I don't know how well that > API has fared in practice. > > I think letting web apps extend the browser's capabilities is a good and > useful thing, and we should do more of it. > I agree that web apps extend the browser's current capabilities is a good way, but there is a limitation that a video file has to be downloaded entirely and assign the video to a video tag than. (File-based Implementation) Users have to wait for file downloaded entirely than watch the video,so the response time is too long to enjoy media files. Media Source Extension is a tool for playing the partial content which is steamed, but the challenge with HTML5 audio and video is still the fragmented support for audio and video formats. However, fragmented video/audio is not a very common format for users. If one file reading request can split into multiple blocks/requests and the content still can be played normally, the response time can be shorten. (Block-based) The file reading request from Device Storage API will split into multiple requests by FUSE like this: static int bindings_read (const char *path, char *buf, size_t len, off_t offset, struct fuse_file_info *info) so file system provider can handle the above request to retrieve the partial content at offset. For example, the content consumer of Video player can play the partial content once it is retrieved. Thanks. > -Ted > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > -- Sean Lee Front-End Software Engineer, Firefox OS Devices Mozilla Corporation _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
