On Sat, Apr 26, 2014 at 4:06 PM, Dylan Butman <[email protected]> wrote:
> A little wrapper might do the trick. What if you mediate all component > queries to the database, and cache a list of returned entities. Anytime any > of those entities change, the component should be rendered (you could even > implement more advanced update to the query result instead of triggering a > new query). Anytime a new entity is added to the database, check if it > would be included in the result of any component query, and mark those > components as dirty. > This is exactly right and the approach I'm exploring, DataScript makes this particularly easy to do since all transactions return a transaction report. Also with entity caching you can re-render efficiently from the root in the time travel case. David -- 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.
