Comment #9 on issue 2016 by [email protected]: Chome does not support pushlets and Comet http://code.google.com/p/chromium/issues/detail?id=2016
Hi Jon, the counting up faster is the problem. Consider a countdown when a Space Shuttle starts. You say a number, wait a moment, say the next number, wait a moment etc. Now, Chromium waits 8 times, then sais eight numbers and after that seems to work properly. What I geuess is that there is a buffer that must be filled before Chromium starts streaming. Okay, a workaround would be to fill the buffer and then come into action. However, Firefox does it without workaround. Now, what is used on pushlets.com is HTML streaming, which is an old fashioned (I would say outdated) way of doing pushlets. The given examples are many years old. The modern way is using the Javascript XMLHttpRequest object. The XMLHttpRequest has a readyState 3, where it gives interim results, and a readyState 4, where it gives the completed result. What I'm trying to point out is that Chromium does not give any interim results in readyStae 3, which I would say is a defect. To make iot easier for you, I've deployed the testcases I gave above on my home page http://www.jounne.com/pushlettest.htm. Just click the link with Firefox and Chromium, and you will see that Firefox counts, while Chromium fails to count. You can also debug the Javascript that is in the html page to see that there is no output in readyState 3. I hope this was helpful. Best regards Johannes -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
