Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
So. I have got web-chat working on socket.io. I’m thinking of using it also for web-pages transportation for not to create more requests to the server. How do you feel about it?
.. Or, probably, one additional request per minute won’t make sense, but it’s easier to work on web-pages in Express. Anyway.
I think of websockets as being a good fit for web applications, not web sites. Transferring web pages would lose the ability to bookmark or to utilize SEO techniques.
However, I certainly think that using websockets in place of AJAX calls is a direction to move in. I’ve provided some resources and information in answers to similar questions:
websocket api to replace rest api?
What is the disadvantage of using websocket/socket.io where ajax will do?