Hi,
Seems possible and fine. Have you already run your programme at your scale ? Did you profile it ? Are you using multiple nodejs processes ?
This might guide you : https://www.jayway.com/2015/04/13/600k-concurrent-websocket-connections-on-aws-using-node-js/.
Regards,
Sven
--
Job board: http://jobs.nodejs.org/
New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 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 unsubscribe from this group and stop receiving emails from it, send an email to nodejs+un...@googlegroups.com.
To post to this group, send email to nod...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/57E001D8.9060902%40bonseletrons.com.br.
For more options, visit https://groups.google.com/d/optout.
Hi Zlatko, thanks for the detailed answer :)
My client is IoT and this brings some limitations...
First I am limited by what libs I can find on the hardware side, then
the IoT can be switched off without proper signaling. And I need to
control that and react on connection loss.
I couldn't find any option for keepalive on either side of the
comunication, I am using:
IoT side: https://github.com/Links2004/arduinoWebSockets
Node.js: https://github.com/websockets/ws