{"action":"created","issue":{"url":"https://api.github.com/repos/facebook/relay/issues/36","labels_url":"https://api.github.com/repos/facebook/relay/issues/36/labels{/name}","comments_url":"https://api.github.com/repos/facebook/relay/issues/36/comments","events_url":"https://api.github.com/repos/facebook/relay/issues/36/events","html_url":"https://github.com/facebook/relay/issues/36","id":100564393,"number":36,"title":"Q: Server rendering?","user":{"login":"stevoland","id":30143,"avatar_url":"https://avatars.githubusercontent.com/u/30143?v=3","gravatar_id":"","url":"https://api.github.com/users/stevoland","html_url":"https://github.com/stevoland","followers_url":"https://api.github.com/users/stevoland/followers","following_url":"https://api.github.com/users/stevoland/following{/other_user}","gists_url":"https://api.github.com/users/stevoland/gists{/gist_id}","starred_url":"https://api.github.com/users/stevoland/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stevoland/subscriptions","organizations_url":"https://api.github.com/users/stevoland/orgs","repos_url":"https://api.github.com/users/stevoland/repos","events_url":"https://api.github.com/users/stevoland/events{/privacy}","received_events_url":"https://api.github.com/users/stevoland/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-08-12T15:01:42Z","updated_at":"2015-08-12T21:04:24Z","closed_at":null,"body":"It seems to me that this would require an API to serialize the store state and rehydrate on the client otherwise the initial client render may differ from the server rendered one.\r\n\r\nIs this feature planned?\r\n\r\nThanks"},"comment":{"url":"https://api.github.com/repos/facebook/relay/issues/comments/130448711","html_url":"https://github.com/facebook/relay/issues/36#issuecomment-130448711","issue_url":"https://api.github.com/repos/facebook/relay/issues/36","id":130448711,"user":{"login":"taion","id":3112159,"avatar_url":"https://avatars.githubusercontent.com/u/3112159?v=3","gravatar_id":"","url":"https://api.github.com/users/taion","html_url":"https://github.com/taion","followers_url":"https://api.github.com/users/taion/followers","following_url":"https://api.github.com/users/taion/following{/other_user}","gists_url":"https://api.github.com/users/taion/gists{/gist_id}","starred_url":"https://api.github.com/users/taion/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/taion/subscriptions","organizations_url":"https://api.github.com/users/taion/orgs","repos_url":"https://api.github.com/users/taion/repos","events_url":"https://api.github.com/users/taion/events{/privacy}","received_events_url":"https://api.github.com/users/taion/received_events","type":"User","site_admin":false},"created_at":"2015-08-12T21:04:24Z","updated_at":"2015-08-12T21:04:24Z","body":"@pkieltyka It's a perfectly reasonable way to handle server-side rendering with Flux - set an aggressive timeout on the server, let some portion of the requests succeed there, and then have clients re-request all the missing data. It lets you split the difference between showing your user a mostly-blank page, and with letting everything be held up by the slowest request."}}