I am second to Will. The queued feature is good for a busy sever which may have to send several messages to the newly-connected client during the download-and-initialization interval. My suggestion is to allow flush the queue when calls create_channel, say, .create_channel(token, flush=True) if flush is True, behaves like in the productive environment. (Do not queue) if flush is False, behaves like in the SDK environment.(Do queue)
2010/12/8 Moishe <[email protected]> > Hi, Will - thanks for the feedback. > > This is an artifact of how the dev appserver works (because of > polling, we need to queue messages), but the Channel API doesn't > behave this way in production. > > -- > 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]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- 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.
