We've still got the transactional problem, so I could see a scenario when we had two requests coming in at the same time. So the get for client A (fails), a post comes in from client B (passes),  then post for client A (fails), then the get for client A (passes). Perhaps that's a bit paranoid. This is one more post, but should always ensure some level of consistency with 2 requests. This is why we need to implement etags for solitude see bug 845967.