Issue 33 in gaeutilities: Session needs to retry on read timeouts

[codesite...@google.com]

Status: Accepted
Owner: bowman.joseph
Labels: Type-Enhancement Priority-Medium

New issue 33 by bowman.joseph: Session needs to retry on read timeouts
http://code.google.com/p/gaeutilities/issues/detail?id=33

Probably the easiest, and most effective way to handle this is to bring the
ROTModel back,except focus it on read instead of write. Session handles
writes with the memcache fallback, so really only need the retries on read.
In order to provide the best tool, ROTModel should still do read and write.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[codesite...@google.com]

Comment #1 on issue 33 by bowman.joseph: Session needs to retry on read
timeouts
http://code.google.com/p/gaeutilities/issues/detail?id=33

This is in via use of the new ROTModel for Session. While ROTModel doesn't
wrap
get_or_insert or get_by_keyname, session doesn't use those methods anyway.

However many puts and deletes are being done with db.put and db.delete. It
may be
best to abstract these with the same timeout retries. Will create another
issue, and
leave this one open until that's resolved also.