title: How can Socket.io and RESTFul work together?
body: <p>(I'm not familiar to RESTFul, please correct me if my concept is wrong)</p>
  
  <p>In RESTFul architecture, we map every action to an URL. If I click "post a article", may it's actually URL <code>http://example.com/</code> and some data <code>action=post&amp;content=blahblah</code>. </p>
  
  <p>If I want to post, but not refresh the whole web page, I can use javascript's XMLHTTPRequest. I post it and then get it's content and insert it to a div in my page. These action is all asynchronous.</p>
  
  <p>Then I know there is something named <code>WebSocket</code> and it's wrapper <code>socket.io</code>. It use "message" to communicate between client and server. When I click "post" the client just call <code>socket.send(data)</code> and wait for server's <code>client.send(data)</code>. It's magical. But how about URL? </p>
  
  <p>It's possible to use the two model both without repeating myself? In other word, every action has it's URL, and some of them can interact with user real-timely(by socket.io?)</p>
  
  <p>Moreover, should I do this? In a very interactive web program(ex. games), the RESTFul is still meaningful?</p>