Re: [w3c/IndexedDB] [IndexedDB] WebAppsWG TPAC F2F agenda (Fukuoka, Sep 19-20 2019) (#288)

TPAC 2019 Web Apps IndexedDB Breakout:

Topics discussed:

* `[SecureContext]` on commit() ? - notes in https://github.com/w3c/IndexedDB/issues/254
* Make autocommit optional - notes in https://github.com/w3c/IndexedDB/issues/34
* KV Storage
  * noted that there are performance concerns since IDB is "slow", but API is great
* Relaxed durability - notes in https://github.com/w3c/IndexedDB/issues/50
* Storing Response/Request objects
  * Mostly about just making them structured cloneable (bags of metadata + a blob)
  * For IDB, would need to define any special indexing - see table in https://w3c.github.io/IndexedDB/#key-path-construct
  * Follow-up: need tracking issue
* Issue backlog triage
  * desire to close out issues we think are not going to happen
  * planned for a day 2 breakout
* version change transactions w/o modifying version number
  * consensus on use case (e.g. PouchDB)
  * proposal: `open(DOMString name, optional [EnforceRange] unsigned long long version, optional DOMString smursion)`; upgrade runs if number is greater or smursion doesn't match. 
  * smursion is expected to be something like hash of database schema description; limited length string that's okay to cache in memory
  * we're not serious about `smursion` as a name :)
  * Follow-up: tracking bug, proposals
* getAll with key and primary key - notes in https://github.com/w3c/IndexedDB/issues/206
* putAll - notes in https://github.com/w3c/IndexedDB/issues/69
* getMany - notes in https://github.com/w3c/IndexedDB/issues/19


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/288#issuecomment-533359849