Does Nick's comment mean that devserver discards async puts if code does not wait for result? This is what I am observing. If so I question usefulness of async altogether. If frontend instance needs to wait for completion anyways then what is all the fuss about? - A few odd cases where you may run a couple of DS ops in parallel.
On Wednesday, November 9, 2011 11:15:45 AM UTC-8, Lenny Rachitsky wrote:
I recently realized that actually, that production waits for them to
complete. Is there any way to reproduce that behavior on the dev
server?
On Nov 8, 9:21 pm, Nick Johnson <nickjohn...@google.com> wrote:
> Hi Lenny,
>
> You should always wait for async requests to finish, including in
> production. If you don't explicitly wait yourself, the appserver will wait
> for them to complete before returning the response to the user anyway.
>
> -Nick Johnson
>
>
>
>
>
>
>
>
>
> On Wed, Nov 9, 2011 at 7:49 AM, Lenny Rachitsky <lenny...@gmail.com> wrote:
> > I'm finding that unit testing async based requests is rather tricky,
> > as the put() often doesn't finish by the time the unit test is run. Is
> > there any way to do a system-wide flush of all async requests on the
> > development server? The only other solution I have is to add if branch
> > that waits for the results to finish if it's on the dev server.
>
> > Any advice would be much appreciated.
>
> > --
> > 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+unsubscribe@googlegroups.com.