Tks Don - I'll give it a shot. If it looks like it would be a good package, generally useful - I'll be in touch :)
Sort of leads to another issue that always tickles (pun intended) the back of my brain - what layer should features be included in? To whit - OpenACS is an open-source project built on AOLserver - which is open-source project built on/in/around TCL which is an open-source project (which is written largely in C in which case you should use SWIG and make the modules available in ALL scripting languages, but I digress)..
To my thinking any feature should be pushed as far DOWN the stack as possible (or practical) to allow it to have the widest reach/appeal and 'bazaar' qualities that will lead to its continual improvement.
So should the 'improved' database API make its way into AOLserver as an optional package someday? Is the distinction that the AOLserver modules are all written in C and OpenACS is a layer of TCL native code on top? That's what appears to be the case to my eye.
