P.S. Did you write how-to for nsproxy newbies? And nsrpc is very interesting especially for send requests from external applications to AOL Server clusters. I didn’t find manuals and how-to for these.

I think, ns_db is very complex and universal but for better performance and code readable is not best idea. Sqlite transaction is performed about by 500 microseconds and complex wrappers make big overhead. And high concurent applications must use parallel readings. On my laptop sqlite database can perform about 1000 write transactions per second and so if my application in the ratio between 1:10 and 1:100 write to read transactions and one client send query every 5 seconds then sqlite-driven application can serve about between 50 000 and 500 000 clients at same times (with enable full sync write for sqlite database file).

db_foreach, hm? Can you do a test using AOLserver’s lower-level ns_db API and see if you can get queries to execute? Also, can you get a gdb backtrace of the crash?