Hi Keakon, Yes, the instance will wait for all pending RPCs to complete before returning the response. Asynchronous RPCs are useful in that they allow you to do other work while the RPC runs.
-Nick Johnson On Tue, Sep 13, 2011 at 6:06 PM, keakon lolicon <[email protected]> wrote: > Hi Google guys, > > I just did a test of async db and memcache operations. > I put or deleted 100 entities and immediately returned. > The async operation call took only 0.01s, the sync one took 0.2s, but both > of their total response time in the backend log was over 200ms, and I could > also feel the latency was longer than a no-op request. > > So I think before the server sending respond to browser, the RPC object > will wait its async operations to finish or get error. > Does it mean if I don't care whether the operation is successful (like > updating a counter), I can do an async call without waiting it by myself? > > ---------- > keakon > > My blog(Chinese): www.keakon.net > Blog source code: https://bitbucket.org/keakon/doodle/ > > -- > 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. > -- Nick Johnson, Developer Programs Engineer, App Engine -- 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.
