-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Russian Doll Caching #168
Comments
Everything's possible, and everything's on the road map. 😬 Looks good to me, but I need to think about what would go into Representable and what is actually the data layers' responsibility. Not top prio right now, though... we can discuss it here. |
what i'm afraid is that, correct me if i'm wrong, representable generate the json at once, taking all properties and serialize it into json. If we want to have russian doll caching, I would guess we want to store json fragments into cache and fetch it every time we need that data. But maybe we can leverage the |
Yes, and no! 😁 Representable as per today calls I'm a bit confused by the |
Sounds like a good plan. Talking about rendering, sorry for the confusion :) |
Is it possible or in the road map?
Let's imagine I update the song but not the artist. It would be nice to get the serialized artist data from cache instead of going through the entire serialization process again.
What do you think?
The text was updated successfully, but these errors were encountered: