Ssgssrcsr differences

1

You need to get all the data before rendering
Due to the need to render a complete component ,
So you must wait until all the data is loaded , Before you can start rendering

So unpackable Technology Big bundjs Open
Download and execute separately

summary

Wait until the previous step is completed , To move on

The server gets all the data ----》 Server rendering —〉
The client is injecting water into the code ----》 Page interactivity

Separately 2 Time ReactDOM.renderToString Method
By splitting React DOM Root The way
Complete the split of server-side rendering
Thus, the problem of delaying the rendering of the server during data acquisition is avoided

Until all components are filled , Can be interactive

Execute when absorbing water js Logic and the process of binding event callback
react It is required that the component tree produced by the front end and the component tree produced by the service end remain one to ,
This will cause the front-end rendering content to overwrite the server-side rendering content

React18 SSR

suspense
Support server-side rendering
Support the loss transmission of the server HTML
Support client selective water absorption

suspense

You can pause the server SSR Work , And after determining the rendering content , Keep going back

Split the rendering , Combined with the ability of selective water injection ,
Speed up the interactive time of the page

Solved the problem 3 A question

1. You need to get all the data before rendering

Static content can be returned first , And continue to return the rest after obtaining the data

2. Only after all the contents are loaded can water be injected

Code splitting can be combined with server-side rendering
HRML After partial rendering , Priority can be given to local water injection

3. Do not interact until all components are filled with water

Give priority to the components that users are interacting with