> If you require more then 666.66 messages per second out of the box, you > should not be using dnode as your message transport. hook.io currently > uses dnode as it's primary message transport. >
Totally agree with you here. I'm developing a social game server-side cluster. We are using socket.io on the servers and flashsocket.io on the client. After comparing dnode and socket.io using benchmarks for server to server communications I selected socket.io here as well. I don't remember exact numbers now but I believe socket.io was about 10 times faster. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
