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 disagree. Identity management is a feature which you only need in > large applications. Smaller apps don't benefit much from it. On the > other hand, identity management involves quite some code and therefore > load time. > > Therefore I'm in favor of keeping it the way it currently is, as a > decorator to ezcPersistentSession. > > > Either someone had problems with too many objects of the same type > > and wrapped an identity session around a current PO version, or he > > never had an issue, which means he doesnt care about wheater an > > etnity is == or !==. > > > Still if that is not an option i would go with your suggestions, > > otherwise ezcPersistentSessionInterface is also a good one. > > ezcPersistentSessionInterface would be more clear, yes. But I'm not > sure if we want to have "Interface" in the names of interfaces. Looks > quite ugly.
And it's against the coding guidelines: http://ezcomponents.org/contributing/coding_standards#class-names regards, -- Derick Rethans eZ components Product Manager eZ systems | http://ez.no -- Components mailing list Components@lists.ez.no http://lists.ez.no/mailman/listinfo/components
