After a bit more playing and reading I think the route of my problem
is that I've designed things so that there is a bit to much contention
in my entity group, I probably shouldn't be running into failed
transactions so much in the first place.
My basic design is that each user account marks the root of an entity
group. And the users documents are children of that group. This seems
like a reasonable design to me, but the problem is that my sync client
hits the group pretty hard. If the user deletes all their documents
locally, then the sync client fires of a separate DELETE request for
each document, all at the same time, and I think that's the root of
the problem. So I guess I need to write a batch delete handler... or
make the client send the DELETE requests in sequence, instead of all
at once.
Let me know if I'm missing a better way... still getting used to web
programming.
Jesse
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
