Hi Ayaz, Probably it's falling back to xhr-polling because you have some firewall or proxy somewhere between your client and your server. Socket.io unfortunately first tries websockets and than falls back to other methods by default which takes some time. The fallback timeout can be configured (see here: https://github.com/LearnBoost/Socket.IO/wiki/Configuring-Socket.IO under "adviced production settings"). If you already know that websockets wont work you also can remove them from the transports list so you wont have to wait for the fallback.
bests, lars On Tue, Jan 22, 2013 at 2:06 AM, ayaz ali <[email protected]> wrote: > hello @Glenn Block Thanks for response yes it falls back to xhr poling > > -- > 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 > -- -- 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
