On 05.01.10 19:52, Chris Anderson wrote:
I don't see how that can help when a user requests a C without knowing that
it is a C and has a parent B and A. I still need to either allow access or
deny it. I don't see how something like this is possible with CouchDB out of
the box, as I don't have the ability to make another request.
This is why modeling as a key/value store will be simpler. If you
store the permissions on C itself, A and B become irrelevant.
Yes, but that would mean that I can not have any inheritance from A->C
and also it would mean that if someone changes access on A or B I need
to distribute that change to possibly millions of C's to keep them in sync.
regards,
Joscha
