Skip to content
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

Prepopulating caches #1021

Closed
frederikcreemers opened this issue Apr 5, 2016 · 2 comments
Closed

Prepopulating caches #1021

frederikcreemers opened this issue Apr 5, 2016 · 2 comments

Comments

@frederikcreemers
Copy link

Unless your pages are hosted as a static site, your server can include initial data with the request for the HTML, determined by the URL. It would be cool if there was a way to prepopulate the cache. For example, when I go to /user/123, the client could send a json representation of that graphql node down to the client. That would save a roundtrip. But depending on the data model, even more roundtrips could be saved by something like this.

@KyleAMathews
Copy link
Contributor

Check out this issue #136

@josephsavona
Copy link
Contributor

Yup, check out #136 as well as isomorphic-relay. That should cover this use-case - please feel free to comment here if you think something's missing and we can reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants