我应该使用快速，客户端反应路由器还是服务器端反应路由器？

Question

I have a simple app which shows a list of comments by users. When a user is clicked the app should go to /users/<id> and show a new page with the users details that will be queried from a MongoDB. Im having trouble to understand where should that logic be.

I saw examples of using the react router in the client like:

render((
<Router>
  <Route path="/" component={App}>
     <Route path="/user/:userId" component={User}/>
  </Route>
</Router>
), document.body)

But also like this in the server side:

<Route name="root" path="/" handler={require('./handlers/Root')}>

And also using express routing:

app.get('/', function home (req, res, next) {
  res.render('layout', {
    reactHtml: React.renderToString(<App />)
  });
});

app.get('/user', function home (req, res, next) {
  res.render('layout', {
    reactHtml: React.renderToString(<User />)
  });
});

Which one is the way to go? What are the differences?

Answer 1

React applications are often initially client-side only, attached to the node as you have noticed. This is what makes it so speedy: only API calls, no re-renders.

Isomorphic apps run on the server too, which is helpful for fallback (no JS) and for SEO and social sharing (Facebook needs to read the HTML meta tags. This isn't at all easy to achieve. You can also get really fancy and hydrate from the server rendering, which accelerates the user experience on those deeper pages.

What you will likely never want is to just render server-side. Kind of misses the full power of React.

Start client, with some good boilerplate like https://github.com/erikras/react-redux-universal-hot-example which will take you all the way to isomorphic and back again.

Answer 2

有了反应你做单页应用程序，所以你永远不会重新加载页面，快递你正在制作一个服务器像apache与PHP