Maximiliano Guzenski

Yes, I notice. But lovell compile everything with "--enable-static". There is another repo that build libvips to aws lambda, that use ldd as I told you. https://github.com/zoellner/sharp-heic-lambda-layer/blob/main/layer/Makefile#L19 How I sad...

I'm trying deploy a aws lambda as a docker image (now aws support that). Your code (and lovell's code) taken long time to compile on my notebook then is hard...

For transitive data, would it be very much against the standard of Flux, return a promise in the component? Sample: ``` javascript var actions = { searchUsers: function(params) { var...

``` javascript var heatBeatTime = 1000*60*10; //10min setInterval(function() { var timeNow = new Date(); var connIds = Object.keys(socketsList); connIds.forEach(function(connId) { var sl = socketsList[connId]; if (!sl) { return true; }...

I'll check the number of TCP connections next time... to quantify (a very small peace): ``` javascript var sockCount = {}; io.on('connection', function(conn) { var username = null; conn.on('data', function(jsonData)...

"close events isn't the most accurate way." But what happens? just there moments that 'close' event doesn't execute? Is there someway to reproduce this issue on development side?

OK, now is the moment that my chat has more then a real online users. total users: 2304, total sockets: 4370 sysctl ``` ruby "sysctl" => { 'net.core.somaxconn' => 16384,...

but anyway, this is something that SockJS SHOULD manage internally. It SHOULD manage this heartbeat.

Now is 5am at Brazil, it is not a issue by few seconds, it is a issue in hours or forever... 90% of my user use a up to data...

there is it... I removed some code (not related to this issue) https://gist.github.com/maxguzenski/5946916