Re: [Zope3-dev] Zope 3 web root
I agree that this is an interesting idea. I have a couple thoughts. * There's something appealing about a collection of files that describe how URLs are mapped to databases, static files, etc. This could serve as a sort of site map for developers. * I agree with Roger this might make sense for small projects. However, for the small projects that I work on I more often need dynamic but not persistent stuff, rather than static file serving. So this proposal would appeal more to me if one could mount non-persistent object, e.g. modules in the URL space (a la Bobo). -Amos ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] RFC: Local Component Management Simplification
Hi, In general I like the proposal, but I have a small nit: registerSubscriptionAdapter's signature indicates that one of its arguments is adapts, but the docstring indicates that it is named required. The same thing is true with unregisterSubscriptionAdapter, registerHandler, and unregisterHandler. Which is preferred, adapts or required? Adapts seems more natural to me since it echoes the name of the adapts() function, but perhaps I'm missing something that makes required more appropriate. -Amos ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
