Here are my latest observations that explain earlier conflicting messages from me on this thread. After adding the timeout change, the behavior changes based on the browser. For chrome the workaround works fine. For Firefox 2.x and latest Safari on Mac it works for me only up to setting the timeout to 2500, when I put higher values the notifications do not show up to the client.
In any case, with even 2500 the behavior is much better. I use a couple of more lines to avoid triggering any issues in production that I have documented here: http://www.gae123.com/articles/gaet/perf-bot-channel.html I would love to further investigate this but I do not have the time. I am still looking for reasons that other code in my application causes this behavior and I would like to hear other experiences on this matter. Thanks, PK -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en.
