Re: [nodejs] Re: Multiple timeouts (lots of...)

Hi Alain, W dniu wtorek, 20 września 2016 02:19:46 UTC+2 użytkownik Alain Mouette napisał: > > 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

Re: [nodejs] Re: Multiple timeouts (lots of...)

You should hop in https://gitter.im/rwaldron/johnny-five and introduce yourself—there's lots of people willing to help with node.js and iot projects On Mon, Sep 19, 2016 at 8:19 PM Alain Mouette wrote: > Hi Zlatko, thanks for the detailed answer :) > > My client is

Re: [nodejs] Re: Multiple timeouts (lots of...)

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

[nodejs] Re: Multiple timeouts (lots of...)

5000 timers per se should not be a problem to measure nor a problem to the app. It's not even a strain to the connections: it amounts to approximately 83 pings per sec, which is not too much. But the bigger question is why do you want this? Just to keep sockets alive? You can set this option

[nodejs] Re: Multiple timeouts (lots of...)

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 Le