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

Server side routing - No SSR routes #24

Open
PEM-- opened this issue Feb 15, 2017 · 3 comments
Open

Server side routing - No SSR routes #24

PEM-- opened this issue Feb 15, 2017 · 3 comments
Milestone

Comments

@PEM--
Copy link
Member

PEM-- commented Feb 15, 2017

Event if it's feasible to setup routes with contents only rendered on the client using the asymetricSsr HOC, these routes create specific cached payloads per route. This increases memory usage and server CPU occupation while these routes could be served far more efficiently if they were tagged properly.

@PEM-- PEM-- added this to the 3.0.0 milestone Feb 15, 2017
@cbilotta
Copy link
Member

I suggest we make three "levels" :

  1. SSR + initialState.
  2. Only initialState (So, tree-walking for data etc, still, but no html rendering).
  3. No SSR, no initialState.

What do you think ?

@j-jackson
Copy link

Sorry for the noob question guys, but would this mean you could potentially have something like /admin as normal client side react, and then all your public facing routes using SSR?

@PEM--
Copy link
Member Author

PEM-- commented Mar 3, 2017

@j-jackson As stated in the description, you can already do it with asymetricSsr. This enhancement concerns the cache handling to avoid filling it with already rendered HTML payload.

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

No branches or pull requests

3 participants