Angular-data: data store and caching for Angular.js

So excited to try this out. An Angular specific smart model layer is something I've been wanting to contribute to the community for a while. Thanks for doing much of the hard work!

Re: Angular-data: data store and caching for Angular.js

#7

Post by watty » Wed, Sep 10, 2014, 5:52 PM UTC

pseudobry wrote: post #3

[deleted] wrote: post #2

[deleted]

author here, what browser are you using?

Chrome, latest version. I think it may have been my internet provider since I was unable to connect to several major sites for a bit.

It's working now.

Re: Angular-data: data store and caching for Angular.js

#8

Post by grumblestumble » Wed, Sep 10, 2014, 5:59 PM UTC

This is great. I've written more application-specific angular data stores than I'd care to admit at this point. From what I understand, this is something that Angular 2.0 will handle better, which was enough for me to justify being too lazy to write a generic library. Thanks for doing the grunt work!

Re: Angular-data: data store and caching for Angular.js

#9

Post by EGreg » Wed, Sep 10, 2014, 6:01 PM UTC

From building http://platform.qbix.com/features/streams I know that there are a lot of challenges here. Caching, throttling and batching requests is of course really useful. My biggest question is how do you implement:

  * multi-user access
  * realtime updates to connected clients, and 
  * offline editing and sync?

When multiple users access a resource, you have to consider things like consistency issues (making sure all users see the same changes applied in the same order). Also other stuff would be nice like access control (perhaps integrated with the publishing user's address book) as well as subscriptions notifications when something changes.

Does anyone know of a library that implements that? It took me a couple years to get everything right in my own library.

Re: Angular-data: data store and caching for Angular.js

#10

Post by aikah » Wed, Sep 10, 2014, 6:02 PM UTC

Why does this has to be an angular library ? there's no need for that.

You could provide a generic js library with a way to opt-in angularjs,that way,your data access layer isnt tied to a presentation framework.

Can I use this lib with Backbone or React ? why this fixation on making everything depend on angular ? like jQuery in the past ? are we destined to repeat the same mistakes over and over again in the client js world ?