Re: [google-appengine] Re: Channel API: a suggestion
Moishe, A flush queue for the dev appserver would be great. Right now it appears that the send_message queue is flushed only after a Task completes or an HTTP Request returns (I tried both). A flush queue would do two things: either clear messages or push them back to the client prior to completion of an AppEngine Task or POST return - I really need the latter more than the former. I'm using Channel to send messages to a progress meter on the client while building ReportLab PDF files. ReportLab offers a progress call back function that only builds up my send-messages until after the file creation task completes. At which point, I get a stream of messages (i.e. too late for a progress meter). Is the current work around to just upload to Production and see it work correctly? Thanks -- You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Re: Channel API: a suggestion
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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Re: Channel API: a suggestion
Great answer! Thanks much - I'll keep a watch out for the enhancement. Steve -- You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: Channel API: a suggestion
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 mois...@google.com 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 google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.comgoogle-appengine%2bunsubscr...@googlegroups.com . 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 google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Re: Channel API: a suggestion
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 google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: Channel API: a suggestion
Moishe, Thanks, good to know. Best, Will On Wed, Dec 8, 2010 at 4:03 AM, Moishe mois...@google.com wrote: 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 google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.comgoogle-appengine%2bunsubscr...@googlegroups.com . 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 google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: Channel API: a suggestion
I got another question. Suppose a client (http browser) opens a channel, then navigates away to another page, but the server keeps sending data down to the channel; then the client is back to the previous page, opens a channel again with the same client id but a different token, will it gets the data sent when it was away from the channel? Will On Wed, Dec 8, 2010 at 9:49 AM, Will vocalster@gmail.com wrote: Moishe, Thanks, good to know. Best, Will On Wed, Dec 8, 2010 at 4:03 AM, Moishe mois...@google.com wrote: 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 google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.comgoogle-appengine%2bunsubscr...@googlegroups.com . 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 google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
