On May 13, 5:02 pm, "Ikai Lan (Google)" <ika...@google.com> wrote: > [...] you can use the pull queues [...] another solution may be an > RPC/callback based infrastructure
Good suggestions but they will make the code more complex. Than again: I can do a development / hosting cost trade-off an that's fine with me. An other approach will be using async urlfetch although this will also need some serious reengineering of our client libraries. Callback and Pull-Que approaches will make our apps less robust and harder to understand and debug. In a urlfetch API the dashboard alone can give you a very good indication if a addressed service starts failing. With pull queues you additionally have to monitor the queue sizes and need to have a feeling what can be considered "normal". With Callbacks you have to build the monitoring all by yourself. Async programming is much harder to get right ... > Just out of curiosity, are you using Java or Python? Python. And all in all I'm very happy with AppEngine. --md -- 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.
