You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: