&& client side rendering services rendered

Client + server side rendering Render

 　　1, a client rendering

　　　　

 

 

 　　　　Usually it will send two requests, the first string of the requested page, the second request data

　　2, the server rendering

　　　　

 

 

 　　　　Of course, ajax and other asynchronous requests will be used, just look at the specific application scenarios

　　3, how to determine the page is rendered client or server rendering

View page source, if the source code, there are corresponding content page, the server is rendering. If there is no corresponding content pages, it is the client rendering

　　　　① view the page source code, and found product information, so here it is a server-side rendering

　　　　　　

 

 　　　　　　

　　　　② view product evaluation, obviously asynchronous operation, do not refresh the page, but a partial update part of the page content, where they use a client rendering technology

　　　　　　

 

 　　　　　　If the client is late dynamically added, begins with the corresponding content source can not be found

　　4. Summary

After analysis, the product list for the server-side rendering, when the response is sent to the browser with the page and data can be found in the review of the source code. 
And product reviews for the client rendering, is a client sends a request, the latter dynamically generated, review the source code can not be found. 
So, a Web site has both server-side rendering, another client rendering.

　　5, SEO issues

The reason why the client and server rendering render binding, the main consideration here SEO search engine optimization. 
ajax asynchronous rendering data, use crawlers can not get that client rendering is not conducive to SEO

　　　　

　　6, usage scenarios

If you need to consider SEO search engine optimization, you must use the server-side rendering, otherwise the client can render faster, better user experience

 

 

 

 

 

 

.