On Mon, 2003-03-03 at 20:41, Tripp Lilley wrote: > 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.)
Hmm... at first I thought this was just a slight generalization of what I was thinking about -- my proposal was really for a set of hooks in Page, not an actual authentication/security implementation (though the implementation should be relatively easy to write with the right hooks). But then I started thinking about other error pages -- which is something I've been trying work through -- and the problems are similar. And there's all sorts of other problems with Webware not being plugin-friendly on the servlet level. Anyway, I started another thread about that. Any concrete ideas about how this could be improved would be good... Ian ------------------------------------------------------- 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
