So this is just a better framework on top of HTTP Bind? It's not true sockets because I still can't open up many simultaneous connections. The max-persistent-connections-per-server was what always annoyed me when it came to using this type of architecture.
Has anyone seen code that manages to multiplex a single connection of this type across multiple tabs within a browser? Is that even possible?
"Then point your browser at http://localhost:4700/static/chat.html, and then open a second browser window and point it at http://127.0.0.1:4700/static/chat.html, and test the application. It’s important to use the two different hostnames localhost and 127.0.0.1 because some browsers limit the number of open connections you can have to each hostname to two. With this limit it is impossible to run two instances of the chat application on the same host. Of course, 127.0.0.1 and localhost should refer to the same local machine, so its a good way of tricking the browser into thinking its talking to separate servers."
Has anyone seen code that manages to multiplex a single connection of this type across multiple tabs within a browser? Is that even possible?
From: http://www.orbited.org/wiki/CherryChat
"Then point your browser at http://localhost:4700/static/chat.html, and then open a second browser window and point it at http://127.0.0.1:4700/static/chat.html, and test the application. It’s important to use the two different hostnames localhost and 127.0.0.1 because some browsers limit the number of open connections you can have to each hostname to two. With this limit it is impossible to run two instances of the chat application on the same host. Of course, 127.0.0.1 and localhost should refer to the same local machine, so its a good way of tricking the browser into thinking its talking to separate servers."