I have never actually found a use case where it is useful to share the same state between the client and the server but then most of the application is rendering paged queries so is fairly unusual. I guess I can see the benefit for static-ish reference data.
Am I missing something? On 18 March 2015 at 17:06, Martin Klepsch <[email protected]> wrote: >> With Firebase, it's really easy - just register listeners for your data in >> Firebase and in those handlers update your app state. When you do writes, >> you write to Firebase directly and its client immediately fires local events >> to any affected listeners so you immediately get the changes locally. Then >> it handles updating the server behind the scenes, and if the update fails >> then it fires events to effectively undo the local changes made earlier. > > On that note it might be worth noting that there is a fairly nice wrapper > library for Firebase.js: > > https://github.com/crisptrutski/matchbox > > -- > Note that posts from new members are moderated - please be patient with your > first post. > --- > You received this message because you are subscribed to the Google Groups > "ClojureScript" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/clojurescript. -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
