[z3-five] Deprecating the old local site support

[Lennart Regebro]

On 7/26/06, Lennart Regebro <regebro at gmail.com> wrote:
> Geez. I'm sleepy or something. I ment *for* 2.11. :-)

That is *removing it* in 2.11. But it might be possible that we can
improve compatibility, in steps.

I did some quick tests, and I think it would be possible to have
Five.site be just a thin layer on top of Five.component. However, the
same incompatibilities arise.

So new plan:

We keep Five.site around in 2.10, for backwards compatibility with
2.9. This means that if you have only software made for
Five.component, you use it. If you have software *only* made for
Five.site, you use it. If you have software made for both, you either
convert Five.site usage to Five.component, or you use Five.site.
Five.site *should* work with Five.component software as well, but it's
hard to test that extensively. Local utility usage should be
compatible over Five 1.2, 1.3, 1.4 and Zope 2.10.

In Zope 2.11, Five.site gets refactored to be a thin layer around
Five.component. Software written for Five.site may have to be changed
a bit. Mainly, utilities will no longer be aq_wrapped. The interfaces
stay the same, though. Software that assumes utilities are wrapped
will need modification for usage with 2.11, but after that
modification, it will still be useable with  Five 1.2, 1.3, 1.4, Zope
2.10 and Zope 2.11.

In Zope 2.12, Five site gets *Baleeted!* and everybody is happy. :)
If you still use Five.site at that point, you will need to change the
site creation and utility registration, and it will then work with
2.10, 2.11 and 2.12, but no longer with 2.8 and 2.9.

Howzat?

-- 
Lennart Regebro, Nuxeo     http://www.nuxeo.com/
CPS Content Management     http://www.cps-project.org/