One more thing I'd like to briefly discuss.
After working on the SimpleDBM class, I realized that this could
actually be very useful to expose to plugin developers. It simplifies
the usage of simple key-val DBs, and provides a unified and installation
independent abstraction for the plugin to use.
So, I'd like to amend the API proposal/discussion with the addition of
simple_dbm.h (file renamed) to the API include directory. We'll mark
this file as "experimental", with no guarantees that we won't break ABI
or APIs until the 3.0 release.
If there are no -1 objections in this discussion, I'll add it to the
proposal which we'll vote on in a few days. If there are objections,
I'll simply leave it out to not make the vote more complex that
necessary, and revisit this again for 3.0.
Thoughts?
-- leif
P.s
For Yahoos: This would make it easier for at least a couple of our
plugins to "abstract" away dependencies we have on internal databases.
I.e. we can "patch" the SimpleDBM to support our internal databases for
our internal build, and to the plugin it'll be transparent (just a
recompile). Not an ideal solution, but better than nothing, and we have
more chance of releasing plugins without making lots of changes /
#ifdef's to the plugin code.
