Ah, interesting, thanks for filling us in, Michael!
Hm, so the current workings of nstcl depend on the fact that all the
drivers nstcl currently supports do not share AOLserver's "each thread
must allocate all handles from a single pool at one time" limitation?
So if down the road nstcl decided to support db drivers based on the
AOLserver C code, you'd want to add in something like the
db_nth_pool_name type stuff that OpenACS has?
On eventually adding the -dbn switch to nstcl, cool! I've yet to
receive much of any feedback on it good or bad, but presumably others
will gradually start using it. :)
Also, for the OpenACS db_* API, the -dbn switch definitely was the
right way to go, but I don't see any harm in also adding your nstcl
style "use this pool and no other" syntax, if people ask for it.
