On Wed, Aug 1, 2012 at 12:13 PM, Jeff Schnitzer <[email protected]> wrote:
> Anything that involves batching in a frontend risks orphaning data in > the frontend... there's just no efective way to ensure that batching > happens and that the queue is purged when "done". It's definitely not bulletproof, but I'd investigate whether I could achieve "good enough" for 99% and be happy that for the rest the client could re-request the score if it didn't reflect their own correct value. As you say, if clients can connect directly to some other more reliable service, maybe that's the way to go. Mixing platforms (GAE url fetch to Amazon SQS, or whatever) would leave me worrying about extra points of failure - you'll now fail if either GAE or Amazon/Heroku go down. Pity. I would imaging a back-end for a game with hundreds of users is something GAE should eat up. Richard -- 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.
