Re: T-Locking and Resolving

[Oliver Zeigermann]

The relation between ParentStore / ExtendedStore and all the others is 
really confusing - I think you are right there. I guess if ParentStore 
will finally take the place of ExtendedStore it should be nice to keep 
the name ParentStore as then there is no need to distiguish it from 
ExtendedStore any more.

Guten Rutsch :)

Oliver

Michael Hartmeier wrote:

On Sat, 2003-12-27 at 16:41, Oliver Zeigermann wrote:


... 

Well, it does transient locking, why not call it TLockingStore or so? 
ExtendedStore is such an ugly name, let's have a nice one for
ParentStore ;)



I kind of like the name because it helps me distinguish between
"aggregating" stores (ParentStore, ExtendedStore) and "aspect" stores
(NodeStore, PermissionStore, ...) that serve individual aspects only. 
I'd like to see something like a ChildStore in the class hierachie ...

TLockingStore doesn't express the resolving functionality.

Guten Rutsch :)

Michael



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]