Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Based on socket.io 0.9.10 default config 1, htmlfile has higher priority over xhr-polling.
I had this idea that xhr-polling (aka long poolling) was a natural choice over websockets when it is not supported. If I keep htmlfile on list, it will be the selected transport for IE6, 7, 8 and 9.
My min req is IE7+, so should I remove htmlfile? I tested xhr-polling on IE7 and 9 and it works fine.
Why is that?
htmlfile streams the data, whereas XHR-Polling is request based, so it’s possible for htmlfile to be more efficient. This site has a good explanation of each transport.
http://showmetheco.de/articles/2011/8/socket-io-for-backend-developers.html