[Pyblosxom-devel] overhaul to remove registry

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

Since CVS is down on SourceForge and I can't check anything in (including
some fixes to some minor screw-ups I did in the last week), I started
doing the overhaul to remove the global registry in the tools module.
This is one of the things that needs to be done in order to fix the
concurrancy issue we have.

Pretty much it's just involving passing the Request object as an argument
into more of the callbacks and other interfaces we have.

For example, the Request object will now hold a copy of the cache but the
tools.get_cache(...) method will still be used to retrieve the cache from
the Request object and, if we don't have one instantiated yet, it'll
create a new one.  So the only change here is that any calls to
tools.get_cache(...) will now have to pass in the Request.

Plugin authors should be aware of storing state in variables on the
module.  They should isntead store state on the Request object in the data
dict.

Any thoughts or advice is more than welcome while I embark on this
exciting journey.

I think after I do this and work some more on the unittesting stuff I
started, I'm going to launch a pyblosxom users site.  Possibly a
SourceForge project.  This additional project will focus on user forums,
documentation, it'll have the Pyblosxom plugin registry, code snippets,
tips, and all that stuff.  It'll focus around installation, usage, flavour
styles, and plugin development.  The existing Pyblosxom project will focus
on the Pyblosxom core.  That's the theory.  Any thoughts on that are more
than welcome as well.  Ultimately, I don't want to run that alone--it'd be
way cool to get one or two additional people to run it with.  So then we
could all split up and head the various components and split up the work.
Or something like that.

That's everything I can think of.  Rock on!

/will

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