Martijn Faassen wrote:
Jim Fulton wrote:
I'm about to merge the jim-adapter branch.
This branch has three major refactorings on it:
- A redesign of the adapter registration machinery
Hey, just some feedback and kudos to you, Jim. Component registration is
now indeed a lot more simple, and more flexible. The ability to have a
utility managed in content space is very useful, for instance.
One pitfall for people is that just registering a utility is not enough
- utilities that were in the site management folder before still need to
be placed somewhere now of course, as they tend to rely on being located
(for instance authentication utilities look up the next utility).
Is it possible to have completely non-persistent local utilities in the
new world?
Not entirely sure what you mean ny non-persistent. Assuming that you mean
"not stored in the database", then yes, by creating a non-persistent component
registry and making it a site manager or making it a base of a persistent site
manager.
Jim
--
Jim Fulton mailto:[EMAIL PROTECTED] Python Powered!
CTO (540) 361-1714 http://www.python.org
Zope Corporation http://www.zope.com http://www.zope.org
_______________________________________________
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
