> So, essentially, CA does the following upon being used:
> 1) Load all the plugins requested. Each plugin will register as being
> used for a specific purpose (which could be "I add methods").
> 2) Verify that all required steps (such as dispatching) have a plugin
> loaded or load the default one.
I find this interesting in an academic sense, and I'd like to see these
ideas fleshed out further. At the moment my immediate questions are:
* Will this lead to more fragmentation of styles or greater
standardization?
* Are there there specific things that are hard to do now that should
be easier, or is this more of a conceptual cleanup?
* How do subclasses work? When you've discovered which module is
going to handle a request, do you 'rebless' the current running
application into that module's namespace? Or does the dispatch
stuff happen at the class level before the app is run?
One thing I can imagine might be possible with a system like this is
being able to do initialization (db, config, log, etc.) before dispatch.
For instance, at the moment it's hard to read your dispatch table from a
config file, because configuration isn't initialized until runtime.
Michael
---
Michael Graham <[EMAIL PROTECTED]>
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/[email protected]/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
