Previously Rocky Burt wrote:
> On Mar 6, 4:52 am, "Alexander Limi" <[EMAIL PROTECTED]> wrote:
> > - TypesTool in CMFCore - adding the threadlocal cache makes that part
> > close to three times as fast, even after the recent Zope 2.10 fix. I think
> > we should do this, as we already subclass TypesT
On Mar 6, 4:52 am, "Alexander Limi" <[EMAIL PROTECTED]> wrote:
> - Rocky's fix to Zope 2.10 fixes the worst of the performance penalty, but
> calling contentmenu.pt still takes 0.76s with his changes - the
> threadlocal cache in TypesTool got it down to 0.27s (with 2.10.2's broken
> code, it took
On Mar 6, 6:36 am, Martin Aspeli <[EMAIL PROTECTED]> wrote:
> Wichert Akkerman wrote:
> > Previously Martin Aspeli wrote:
> >> Yeah, I know. :)
>
> >> My point in the bug thread is that I *think* the solution is to make
> >> sure slashing of links is always consistent: if it's folderish, put / at
>
I assume (but haven't checked) you upset the W3C police with that change ;)
— Alexander
On Tue, 06 Mar 2007 01:23:34 -0800, wichert
<[EMAIL PROTECTED]> wrote:
Author: wichert
Date: Tue Mar 6 09:23:34 2007
New Revision: 13585
Modified:
CMFPlone/trunk/skins/plone_templates/batch_macros.p
Wichert Akkerman wrote:
Previously Martin Aspeli wrote:
Yeah, I know. :)
My point in the bug thread is that I *think* the solution is to make
sure slashing of links is always consistent: if it's folderish, put / at
the end, if not, don't.
We can always put a / at the end; Zope should handle
Previously Martin Aspeli wrote:
> Yeah, I know. :)
>
> My point in the bug thread is that I *think* the solution is to make
> sure slashing of links is always consistent: if it's folderish, put / at
> the end, if not, don't.
We can always put a / at the end; Zope should handle that correctly.
