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
It turns out that I spoke too soon about this. Probably I just did not
properly refresh the browser when I said that changing the value from
500 to 5000 works; channel notifications do not work after such a
change so this is not a workaround.
PK
--
You received this message because you are
Issue 4946 http://code.google.com/p/googleappengine/issues/detail?id=4946
seems to be the same or closely related with what I reported here so
please star it if you want to see a resolution.
PK
www.gae123.com
--
You received this message because you are subscribed to the Google Groups
Google
Hi,
In your code need to set the socket POLLING_TIMEOUT_MS. I've tested
this, works correctly.
goog.appengine.Socket.POLLING_TIMEOUT_MS = 5000;
DevSocket is exported as Socket at the bottom of the jsapi file.
Robert
On Mon, Jun 6, 2011 at 23:48, PK p...@gae123.com wrote:
Issue
Once more, thanks Robert for pointing this out.
I patched the value to 5000 from the original value of 500 and things
are much better...
PK
www.gae123.com
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to
Thanks Nick.
Is so frequent polling really necessary though? My feedback is that
you need to look at this implementation again. In my app, I would be
fine to wait up to 5-15 seconds for channel notifications on the dev
server. If other apps are more sensitive maybe the interval can be
made
Have you tried setting the polling timeout?
goog.appengine.DevSocket.POLLING_TIMEOUT_MS
http://code.google.com/p/googleappengine/source/browse/trunk/python/google/appengine/tools/dev-channel-js.js#5234
Robert
On Fri, Jun 3, 2011 at 13:23, PK p...@gae123.com wrote:
Thanks Nick.
Is so
