Re: [Pyblosxom-devel] New entry triggered events.

[will <wi...@bl...>]

On Mon, 27 Jan 2003, Wari Wahab wrote:
> > 
> >  1. kick off and read the ini file to configure itself
> >  2. instantiate its plugins
> >  3. get a full entry_list of all the entries
> >  4. generate a list of differences between the two lists (which
> >     will be changes since the last run)
> >  5. kick off some handler for plugins to do their thing
> 
> How would you do 2. and 5.? Sound's different from the plugins in
> pyblosxom right now :)

I'm not sure yet.  In my opinion, we don't have to worry about the 
overhead of setting everything up when pyblosxom.cron runs.  So it can 
kick off and load every plugin--it doesn't really matter since we don't 
need to keep the total runtime to a minimum like we do with pyblosxom.cgi.

However, assume we have a bunch of pyblosxom.cron specific plugins--we 
don't want pyblosxom.cgi to load them all every time it kicks off.

I'm thinking we might want to re-architect things, but I'm not sure what's 
the easy/nice approach to do it.  Seems to me that we should have in the 
config file a list of the modules that should get loaded and only load 
those rather than our current setup where we load anything in the 
directory.

If we do that, then both pyblosxom.cgi and pyblosxom.cron can have the 
same system because we're not incurring the overhead involved in setting 
up things we're not going to use in pyblosxom.cgi when pyblosxom.cgi kicks 
off.

We could do this in the ini file (I think--I actually have no experience
with ConfigParser stuff yet) or in config.py.  Whatever we do, we should
centralize the configurations for xmlrpc, pyblosxom.cgi, and
pyblosxom.cron so we're not sending people hither tither configuring this.

/will


-- 
whatever it is, you can find it at http://www.bluesock.org/~willg/
except Will--you can only see him in real life.