On 08/07/2008, Tobias Schlitt <[EMAIL PROTECTED]> wrote: > Hi Hans! > > > On 07/08/2008 04:02 PM Hans Melis wrote: > > Derick Rethans wrote: > > 8<-- snip --8< > > >> I don't quite see why you need this set stuff... it seems all so > >> complicated. > > > That's my problem with this new proposed stuff for PO. While it sounds > > nice in theory, for now it looks like an overcomplicated API. > > > Where exactky do you feel it's overcomplecated? I don't think it is the usage of the system that is overcomplicated, it's more the inner workings of it. However, this is a complex matter I remember from our discussions and from what I see you write. I'm not sure if it is actually possible to make this much easier. It makes sense if you think about what is really going on here: "a cache of loose objects that can be queried in any way, should be as efficient as possible and that should always be up to date. " This is not simple. It does feel a bit tangled up I must admit, many ifs and buts that are not very clear right away.
>$session = new ezcPersistentIdentitySession( > $innerSession, > new ezcPersistentIdentityMap() > ); What is the reason for exposing the identity map like this? I understand you can roll your own identity map and use it easily this way, but when would you want to do that? Frederik -- Components mailing list [email protected] http://lists.ez.no/mailman/listinfo/components
