Thank you for your share. That means when there are too many connections at the same time, you can't make socket.io connection ? Any that must be big application ?
I'm very curios on this pb because I'm working on a project that uses socket.io Thank you On Friday, August 2, 2013 6:52:51 PM UTC+2, Matt Sergeant wrote: > > > On Fri, Aug 2, 2013 at 9:26 AM, bodo <[email protected] <javascript:>>wrote: > >> "random clients just plain not working" => what do you mean ? I don't >> find any problem with socket.io for now >> > > I mean they just don't successfully make socket.io connections and don't > trigger timeouts. > > > I don't find any problem with socket.io for now > > Most people don't until they start to gain users who actually let them > know of problems. And it's impossible to debug those problems because > there's no error messages and you can't emulate their network/environment > perfectly. > > There's a reason they re-wrote socket.io from the ground up for 1.0 > (still un-released). Because the current version just doesn't work in > enough places. > > Matt. > > -- -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
