Paul Taylor

@jameslaneconkling after investigating this a bit, I think I know why I punted on making this work for the old mode. The commit 1571eeb73b9ed02fa7a73b5af9154ac42a5d4543 will fix it for the case...

@jameslaneconkling you're right, the `recycleJSON` version should be onNext'ing value at minimum. Will look into it now.

@jhusain I believe this was closed by #27

@drFabio the `$expires: 0` atom not showing up in the response result is a known bug (falcor merges the atom into the cache, but the followup `get` sees it as...

@drFabio that's up to the Netflix team ¯\\_(ツ)_/¯ but I seriously doubt it. We've refactored or rewritten most of the client and router for better performance, deep React integration, and...

@jhusain could we not have a prototype with these methods, then use `Object.create(falcorJsonProto)` to create the JSON branch nodes? For some reason this just reads really well to me: ```...

@jhusain the JSON structure would still be serializable (one could still write `model.getCache()` to localStorage), and the behavior would survive deserializing assuming the cache was still accessed through falcor (`new...

How do you think we should tackle this? Easiest way seems to be reintroducing sweet.js as an intermediate step in the build process to compile in/out the asserts depending on...

@sfrdmn the cache was designed to be serialized (to disk, local storage, redis, etc.) to allow hydrating on startup if you want. You can pass an `onChange` handler in the...

@erikakers sorry for the late reply. My gut instinct here is to investigate whether Falcor is parsing the String `"2015"` into a Number. If that's true, your route handler would...