Hi Martijn. This is very helpful and I appreciate your post. I'll be taking a closer look at the example for sure. I quite like what is happening with these solutions. I like the z3c.dobbin's slick zope schema implementation and would like to attempt a container implementation much along the lines of what you are demonstrating.. It would make rdb quite transparent. Another interesting point about rdb and wsgi is what to do about site managers without zodb. Typically you set up your authentication and core utilities either within gsm or local site manager. When you are registering utilities, many of the utilities set up folders within the gsm or local site manager. Thinking about authenticators here but there are many others also .It has me asking whether I ought to be doing along these lines to refactor. I am aware of things such as repoze.who and authkit that could be of benefit here. I am hoping to hear of experience from folks moving in this direction to see how this is being handled. Many thanks. Regards, David ----- Original Message ----- From: Martijn Faassen <faassen@startifact.com> Date: Monday, May 26, 2008 1:54 pm Subject: [Zope-dev] Re: Zope and Storm (SQL)
David Pratt wrote:
Martijn. Actually I think I said prevalent, not relevant :-).
True, you did, it's just that you connected these topics particularly with refactoring legacy code, while I've been thinking more about them in the context of new code.
I agree about relevance in both circumstances so highlighted container, location and traversal as key issues for refactoring legacy code. I am concerned about retaining heirarchical arrangements and being able to use existing traversal methods. I really like what you are doing here and will look at your implementation. I appreciate you for pointing this out. Many thanks.
The sketchy implementation is here:
http://svn.zope.org/grokapps/rdbexample/
(the declarative-directives branch is the only one that currently actually "works", by the way).
In particular the interesting bits are in the sub-package 'megrok.rdb'. We're hoping to convert this code to use zope.sqlalchemy, and also start implementing some of the configuration details we discussed in another thread. Right now we're focusing on making this work for Grok, but you know we have the habit of splitting off more commonly useful code over time, and external contributions can of course accelerate that work. :)
Regards,
Martijn
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )