Ian Bicking wrote: >If this seems like a hack, I think the best way would be to formalize >the notion of a default action, since that's what you're really asking >for. I think it's more robust, because you'll still be able to use GET > > This is something that I've been thinking about a lot.
I love the actions stuff in WebKit; and I think that EVERY transaction should really have an action; basically, each transaction is calling a method of an object. Why should the "writeHTML" be any different? This really started to seem obvious to me as I worked on security checks for a "UserAccountKit" that we're working with, and had to do all the security checks twice: once for actions, and once in the writeHTML tree of methods. I would support an architectural change that made EVERY transaction an action... it would be great; we'd get preAction(), postAction() and the main action() for every transaction; which among other things would allow us to leave awake() and sleep() for the WebKit internals (or superclass internals). If the default action just called an output method, so be it. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Webware-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-devel
