Charlie Clark-3 wrote:
> Am 03.05.2007 um 00:50 schrieb Alexander Limi:
>>> At present, Archetypes-based content types cannot be used with a
>>> factory (I
>>> tried hard, but there are some acquisition-related/factory related
>>> I'd like to refactor this, but we can't for Plone 3.0 at least.
>> Right. Obviously, we'd like to do this "the proper way", but we
>> can't do that for a while yet.
> I'm sorry but it's -1 from me. The change is unnecessary and the
> problem seems to be with Archetypes and not the CMF. In my view it is
> incorrect to change the infrastucture to compensate for the
> deficiencies of a component. If you need it in Plone you can add it
> as a patch.
I'm not entirely convinced the problem is in AT, and I think we are
conflating two different issues here. One is an observation of Tres' that AT
has a function that could perform more cacheing. That's a good point, and
may mitigate some of the performance issues by cacheing at a higher level,
but it doesn't mean there aren't further opportunities for improvements to
the underlying code.
The other issue is some code in TypesTool which is making a lot of calls to
a procedure in Zope which is unlikely (impossible?) to ever return a
different result until Zope is restarted and new products are detected.
If the two are orthogonal, and we already have a sane patch, then why not
(at least if we can get some tests in place) fix the one at the CMF level
and deal with the other Archetypes issue separately.
View this message in context:
Sent from the Zope - CMF list2 mailing list archive at Nabble.com.
Zope-CMF maillist - Zope-CMF@lists.zope.org
See http://collector.zope.org/CMF for bug reports and feature requests