Closed Bug 1191774 Opened 9 years ago Closed 9 years ago

Kinto.js next steps discussion

Categories

(Firefox OS Graveyard :: Sync, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
FxOS-S5 (21Aug)

People

(Reporter: ferjm, Assigned: mbdejong)

References

Details

We need to sync with the Cloud Services team regarding the next steps for kinto.js and see which changes/improvements do we need in general and for the FxOS Data Sync project in particular (i.e. a lite version for fxos)
Assignee: nobody → mbdejong
Target Milestone: --- → FxOS-S5 (21Aug)
Blocks: fxos-sync
I started getting involved in testing out kinto.js and participating in discussions on irc and https://github.com/Kinto/kinto.js/issues?utf8=%E2%9C%93&q=author%3Amichielbdejong+

The new RemoteTransformers which just landed are great for our purposes, I'm already using them.

I will also try out http://kintojs.readthedocs.org/en/latest/extending/#custom-database-adapters so we don't store data twice - once inside kinto.js IDB and once in the DataStore for e.g. 'places' (= browser history). Our custom adapter would directly be the history adapter, then.
We got a pretty fluid discussion going via https://github.com/Kinto/kinto.js/issues and the #fxos-sync irc channel. I will also write a blogpost on http://www.servicedenuages.fr/ about how we use Kinto RemoteTransformers, and forward the link to dev-gaia.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.