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

[Wari W. <wa...@ce...>]

* will <wi...@bl...> [030126 01:00]:
> I'd probably make this a completely separate script from
> pyblosxom.cgi--I can't tell if that's what you're implying or not.  It
> would use the same ini file to figure out pyblosxom settings, but have
> a different plugins directory to limit unneeded overhead of
> initializing plugins that aren't needed.  So then it's run-time
> algorithm would look like this:
> 
>  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

Yes sir, this is how I envisioned the script to work, it's gotta be
seperate, a queue don't make sense cause you have to browse your site
everytime you want something to happen. If it's seperate and runs from
cron, entries scp'ed to blosxom's directory or using xmlrpc would work
as expected.

I can do a simple walk, store it in a db, and a later run would 'notice'
the changes if any. Simple actually.

How would you do 2. and 5.? Sound's different from the plugins in
pyblosxom right now :)

I was thinking of doing the plugins like the load() mechanism, which
would mean 1, 3, 4, 5, I think.

-- 
Regards: Wari Wahab
Senior R&D Engineer
Celestix Networks
http://www.celestix.com/