Include archetypes.schematuning, but make sure it supports multiple sites per instance
AT.Schematuning seems to offer a nice performance boost, but it doesn't appear to include the idea that there could be multiple sites in an instance with different schemas.
ah, excellent! then, I'll mark this closed and completed! thanks, eric!
AdminEric Steele (Admin, Plone) commented
Jon: I believe the functionality provided by archetypes.schematuning has been merged into archetypes.schemaextender itself.
Hedley, any update on this?
Hedley Roos commented
In answer to Andreas: that functionality is in trunk. I'll ask Jens to make a release.
Alec Mitchell commented
Should be easy enough to switch it from a global cache to a per instance cache. Or simply customize the cache keys to include site path. Perhaps it could be adjusted to simply cache the filesystem schema and leave the more dynamic per-site/per-instance schema bits dynamic? Doesn't schema extension allow more than just site-wide schema modifications?
Yes, for example, it is not uncommon to schema-extend a core Plone content type in different ways for two different sites in the same Zope instance.
Andreas Jung commented
Different schemas for different Plone sites within one Zope instance?