Right now, yeah, the workaround is to try it in prod. Obviously that's not optimal.
We're going to add presence to the Channel API so that your application knows when a client using a channel is connected/ disconnected. Since the dev appserver will need to simulate this, it could mirror production more closely at this point: if the client's not connected, drop the messages; if it is connected, queue them. Timing issues may be different (connecting in dev will be much faster, for instance) but it'll be more consistent conceptually between dev & prod. (especially since there'd be no concept of flushing the queue in production) No firm ETA on this yet but it's in the pipeline. In response to Will's question about opening a channel, navigating away, then returning to the page: in production, any messages sent when the client's not connected to receive them will be dropped. -Moishe -- 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.
