WebAPI/2013-12-10
From MozillaWiki
< WebAPI
« previous week | index | next week »
WebAPI Meeting Details
- Tuesday 2013-12-10 - 8:00 am Pacific
- Dial-in: Audio-only conference# 98413
- People with Mozilla phones or softphones please dial x4000 Conf# 98413
- US/Toll-free: +1 800 707 2533, (pin 4000) Conf# 98413
- US/California/Mountain View: +1 650 903 0800, x4000 Conf# 98413
- US/California/San Francisco: +1 415 762 5700, x4000 Conf# 98413
- US/Oregon/Portland: +1 971 544 8000, x4000 Conf# 98413
- CA/British Columbia/Vancouver: +1 778 785 1540, x4000 Conf# 98413
- CA/Ontario/Toronto: +1 416 848 3114, x4000 Conf# 98413
- UK/London: +44 (0)207 855 3000, x4000 Conf# 98413
- FR/Paris: +33 1 84 88 37 37, x4000 Conf# 98413
- Gmail Chat (requires Flash and the Google Talk plugin): paste +1 650 903 0800 into the Gmail Chat box that doesn't look like it accepts phone numbers
- SkypeOut is free if you use the 800 number
- WebAPI Vidyo Room / London-Allo Allo / Toronto-Spadina
- Join irc.mozilla.org #webapi for back channel
Notes below archived from etherpad: https://etherpad.mozilla.org/webapi-meetingnotes
Notes
- DataStore C++ wrapper
- because we ❤ workers (and ...
- 1. no IDB in workers (yet!)
- 2. DataStore is written in JS
- because we ❤ workers (and ...
- Jan thinks we may want a dedicated thread for the quota manager
- allows for IPDL access from child processes, threads, etc.
- short term, Ben suggests we don't touch quotamanager for async idb
- long term, for localStorage and IDB ... don't have a grand plan yet
- at this point, unclear about dedicated thread for quota manager
- Ben needs time to investigate this more
- Jan points out that our graphics compositor uses IPDL for communication so speed can't be too much of an issue
- one idea: third type of storage (temporary, persistent, ___)
- bookmarking (aka installing) webpage to homescreen
- not "temporary" anymore
- move from temporary to persistent? PITA
- new: default
- webpage data put here is temporary
- bookmarked page data here is no longer persistent
- pages can still use temporary for the majority of, say, transient data (ex. tweet stream)
- to continue the Twitter example, drafts are put in default area
- persistent would still have a prompt
- bookmarking (aka installing) webpage to homescreen
- another idea (from Alex Russell): notifications for low storage events, etc. to take action on their stored data
