WebAPI/2014-04-15
From MozillaWiki
< WebAPI
« previous week | index | next week »
WebAPI Meeting Details
- Tuesday 2014-04-15 - 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
- Ideas about educating people about DataStore usage
- fallout from some gaia work that was done without lots of knowledge of how DataStore works
- https://wiki.mozilla.org/WebAPI/DataStore
- http://airpingu.github.io/data-store-api/index.html
- issues
- keys (Ehsan can fill in details here)
- large JSON files
- pseudo-schemas built on top that require coordination between different apps
- ways to fix
- better docs on MDN
- example code
- presentation on Air Mozilla?
- link to the docs from everywhere
- specific communication with gaia teams
- do people have ideas of how to make this more usable?
- better name for sync function?
- change interface to make it harder to use in unintended ways
- Marcos thinks that we should perhaps address issues in IndexedDB v2
- baku would like to work with DataStore users to find their pain points
- name bikeshedding
- replace entirely with Activities for ex., data exchange?
- potentially poor method of getting updates of underlying data modifications
- could maybe work for 2 apps communicating but unclear for > 2 apps
- issues
- recap from recent Extensible Web Summit and W3C meetings
- Service Workers is a lot further along
- Manifest going well and Microsoft interested now
- renewed interest in standardizing Web Activities: http://oksoclap.com/p/8pYs44D5CQ
- minutes from many Extensible Web Summit meetings
