On Mon, 3 Mar 2003, Geoffrey Talvola wrote: > I'm not convinced. From a design perspective I find it better to use a > subclass. Or perhaps a Mixin. Just something that keeps the authentication > stuff separate from Page.
-1 on subclass, +1 (about forty times over :) ) on a Mixin. I've been following this thread and it seems to me that all of this behaviour built around Page is just -begging- for Mixins or delegates of some sort and documentation of an interface for adding behaviour to pages through them (e.g., the base Page class will guarantee to call through the chain of delegates in a particular order, etc.) This way, we can provide each of the building blocks for authentication, and each particular piece can be included, left out, overridden, etc., without having to subclass for each oddball corner case. "I walk into this room, and, I'm thinking 'plugins'!" :) ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
