Re: [Components] PersistentObject: Interface ezcPersistentObjectSession

2009-04-29 Thread Derick Rethans
On Sat, 25 Apr 2009, Frederik Holljen wrote: > On 25/04/2009, Tobias Schlitt wrote: > > > > On 04/24/2009 11:17 PM Frederik Holljen wrote: > > > > > I propose: > > > ezcPersistentSessionBase or Definition for the interface > > > ezcPersistentSessionIdentityDecorator for the decorator > > > > > So

Re: [Components] PersistentObject: Interface ezcPersistentObjectSession

2009-04-29 Thread Derick Rethans
On Fri, 24 Apr 2009, Tobias Schlitt wrote: > On 04/22/2009 11:28 PM Benjamin Eberlei wrote: > > > I see no disadvantages from forcing the current session from > > overtaking the identity map changes. Its a natural feature addition > > that shouldn't cause any backwards compability issues. > > I

Re: [Components] PersistentObject: Interface ezcPersistentObjectSession

2009-04-25 Thread Frederik Holljen
On 25/04/2009, Tobias Schlitt wrote: > Hi all, > > > On 04/24/2009 11:17 PM Frederik Holljen wrote: > > On 24/04/2009, Tobias Schlitt wrote: > > >> On 04/24/2009 09:10 PM Frederik Holljen wrote: > > > >> Yes. Let me elaborate a bit more: The problem with the decorator > >> (ezcPersistentIden

Re: [Components] PersistentObject: Interface ezcPersistentObjectSession

2009-04-25 Thread Benjamin Eberlei
Personally i think Base <-> Abstract is almost the same from the meaning, which makes naming an interface Base somewhat misleading. In light of all the arguments Tobys initial proposed name is probably the best. greets, Benjamin On Friday 24 April 2009 23:17:13 Frederik Holljen wrote: > On 24/0

Re: [Components] PersistentObject: Interface ezcPersistentObjectSession

2009-04-25 Thread Tobias Schlitt
Hi all, On 04/24/2009 11:17 PM Frederik Holljen wrote: > On 24/04/2009, Tobias Schlitt wrote: >> On 04/24/2009 09:10 PM Frederik Holljen wrote: >> Yes. Let me elaborate a bit more: The problem with the decorator >> (ezcPersistentIdentitySession) is, that it is not "instanceof >> compatible" w

Re: [Components] PersistentObject: Interface ezcPersistentObjectSession

2009-04-24 Thread Frederik Holljen
On 24/04/2009, Tobias Schlitt wrote: > Hi Fred, > > > On 04/24/2009 09:10 PM Frederik Holljen wrote: > > 2009/4/24 Tobias Schlitt : > > >> On 04/22/2009 10:08 PM Frederik Holljen wrote: > > >>> Hmm... isn't that a bit obfuscated? How are people supposed to know > >>> (without looking in the do

Re: [Components] PersistentObject: Interface ezcPersistentObjectSession

2009-04-24 Thread Tobias Schlitt
Hi Fred, On 04/24/2009 09:10 PM Frederik Holljen wrote: > 2009/4/24 Tobias Schlitt : >> On 04/22/2009 10:08 PM Frederik Holljen wrote: >>> Hmm... isn't that a bit obfuscated? How are people supposed to know >>> (without looking in the docs) what the purpose is for each of them? >>> What exactly (

Re: [Components] PersistentObject: Interface ezcPersistentObjectSession

2009-04-24 Thread Frederik Holljen
2009/4/24 Tobias Schlitt : > Hi Fred, > > On 04/22/2009 10:08 PM Frederik Holljen wrote: >> Hmm... isn't that a bit obfuscated? How are people supposed to know >> (without looking in the docs) what the purpose is for each of them? > >> What exactly (short in your words) does the new one do? > > ezc

Re: [Components] PersistentObject: Interface ezcPersistentObjectSession

2009-04-24 Thread Tobias Schlitt
Hi Benjamin, On 04/22/2009 11:28 PM Benjamin Eberlei wrote: > I see no disadvantages from forcing the current session from overtaking the > identity map changes. Its a natural feature addition that shouldn't cause any > backwards compability issues. I disagree. Identity management is a feature

Re: [Components] PersistentObject: Interface ezcPersistentObjectSession

2009-04-24 Thread Tobias Schlitt
Hi Fred, On 04/22/2009 10:08 PM Frederik Holljen wrote: > Hmm... isn't that a bit obfuscated? How are people supposed to know > (without looking in the docs) what the purpose is for each of them? > What exactly (short in your words) does the new one do? ezcPersistentSession Basic, origin

Re: [Components] PersistentObject: Interface ezcPersistentObjectSession

2009-04-22 Thread Frederik Holljen
On 22/04/2009, Benjamin Eberlei wrote: > Still if that is not an option i would go with your suggestions, otherwise > ezcPersistentSessionInterface is also a good one. I'd go with that... -- Components mailing list Components@lists.ez.no http://lists.ez.no/mailman/listinfo/components

Re: [Components] PersistentObject: Interface ezcPersistentObjectSession

2009-04-22 Thread Benjamin Eberlei
I see no disadvantages from forcing the current session from overtaking the identity map changes. Its a natural feature addition that shouldn't cause any backwards compability issues. Either someone had problems with too many objects of the same type and wrapped an identity session around a cur

Re: [Components] PersistentObject: Interface ezcPersistentObjectSession

2009-04-22 Thread Frederik Holljen
Hmm... isn't that a bit obfuscated? How are people supposed to know (without looking in the docs) what the purpose is for each of them? What exactly (short in your words) does the new one do? Frederik On 22/04/2009, Tobias Schlitt wrote: > Hi all, > > so far, the interface of ezcPersistentSess

[Components] PersistentObject: Interface ezcPersistentObjectSession

2009-04-22 Thread Tobias Schlitt
Hi all, so far, the interface of ezcPersistentSession is only fixed by our BC standards. Now that ezcPersistentIdentitySession is introduced, we'll need to have an interface that both of these will implement, to be able to store them in ezcPersistentSessionInstance. Since ezcPersistentSession (the