Quoting Dominik Huber <[EMAIL PROTECTED]>:

> Phillip's Proposal:
> Furthermore, I propose to remove the |IDefaultLayer| interface. We've
> been using the |default| layer as a connotation of "always being
> available unless overridden by a more specific layer." However, this
> does not apply all the time: When the |default| layer is not included in
> a specific skin, nothing from the |default| layer will be found even
> though the ZCML statements suggest that it would always be available. I
> therefore propose to make the |default| skin layer an alias for
> |IBrowserRequest|. Anything registered for |default| will obviously
> always be available then, no matter what your skin layer looks like.
>
> -1
> I really appreciate that I can disable all registrations if I do not
> derive a skin from the default layer. That's very important use case for
> us. We introduced a minimal layer that is providing only the most
> important functionality like traversers etc. Regularly we derive
> end-user skins from this minimal layer and then we register all views
> explicitly so that we have full controll over accessibility of information.

Very well, I didn't think there were use cases for this. I guess there are. 
Thanks for
letting me know! I've given the proposal a general overhaul and ripped out this
suggestion as well. Please revise it again and let me know if you see any other 
issues.

Continuing-to-RFC-ly

Philipp


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com

Reply via email to