Node.js: I already use socket.IO for chat, what about transporting Web-pages also through it?

Question

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.

score 1 · Answer 1 · answered Aug 25 '11 at 08:47

1

Those pages could not be found by any search engine. For private areas (where you have to be logged in), why not? I think the only disadvantage would be, that you could not load multiple things together.

answered Aug 25 '11 at 08:47

Van Coding

24,244
24
88
132

Multiple things together? If I put tags into page would they load parallel, isn't it? So, what would load not together? – Ben Usman Aug 25 '11 at 11:02

score 1 · Accepted Answer · edited May 23 '17 at 12:21

1

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?

edited May 23 '17 at 12:21

Community

1
1

answered Aug 26 '11 at 10:02

Tauren

26,795
42
131
167

Yes. I meant exactly something like that. – Ben Usman Aug 26 '11 at 13:16
And, so - I won't have an ability to handle more than ~6500 connections on the same time on one server? For example chat. – Ben Usman Aug 26 '11 at 13:26

Node.js: I already use socket.IO for chat, what about transporting Web-pages also through it?

2 Answers2