WebAPI/2013-12-17-take2: Difference between revisions
< WebAPI
Jump to navigation
Jump to search
(Created page with "* https://github.com/mozilla/localForage * W3C working draft for DataStore API ** http://airpingu.github.io/data-store-api/index.html ** lots of discussion about strings as ke...") |
No edit summary |
||
| Line 22: | Line 22: | ||
** We're worried about exposing wifi versus data | ** We're worried about exposing wifi versus data | ||
** Marcos wants to know more about the use cases, directly from developers | ** Marcos wants to know more about the use cases, directly from developers | ||
[[Category:Web APIs]] | |||
[[Category:Meeting Notes]] | |||
Latest revision as of 22:52, 1 October 2014
- https://github.com/mozilla/localForage
- W3C working draft for DataStore API
- http://airpingu.github.io/data-store-api/index.html
- lots of discussion about strings as keys
- people will take their discussion to the mailing list
- Ben's worker stuff landed \o/
- Blobs and Inter-App Communication API
- https://bugzilla.mozilla.org/show_bug.cgi?id=951246
- Ben blames khuey for this issue
- synchronous re-entrant message ports needed for Shumway
- khuey going to work on this
- (only for chrome Shumway usage)
- locale-based sorting in IDB for DataStore
- Jonas suggests Ben Kelly may be interested in doing this
- will need API design and implementation
- Network Information API
- Gene and Fernando will work on the API, Marcos is doing use case design
- Jonas thinks we should expose the connection type and the bandwidth number for mobile connections
- Gene says that exposing the bandwidth number is not implementable on all platforms
- Jonas thinks that we should use a combination of known bandwidth values per connection type and also gathering connection statistics from network requests handled by Gecko
- We're worried about exposing wifi versus data
- Marcos wants to know more about the use cases, directly from developers