Luci Brăn

@apaatsio Yes, something like that might indeed be clearer.

The only potential use case might be data you never wish to sync, but perhaps a different local persistence mechanism may work better. It may make sense to collapse the...

In the app this was built for initially, the local source was the authoritative one, so a single callback was preferable. There could be a callback passed to `syncDirtyAndDestroyed` or...

It already works without CORS on PhoneGap by whitelisting the server. We do control the server, but have little time to fix it atm. Thanks for the tips. This issue...

You can't be at peace, at least not at the moment :) You can do a manual sync periodically, which is what I'm doing atm.

That may be what I'll do. I'll look into this more closely, perhaps next week.

@kurtmilam Pretty nice. I think I'd prefer keeping a separate record that maps between keys and such data, rather than wrapping everything.

I was thinking of something simpler, like `localStorage['__dirty__'] = ['/foo/bar/1', '/foo/bar/2']`. When a model is changed, it gets added to the dirty list, when the server gets the update the...

This is again similar to what I had in mind, but haven't had time for. Looks nice.

I was never comfortable with compiled JS in the repo. It seems to me that someone could easily submit a pull request where the .coffee and compiled .js differ (either...