> Ok. I've read the Document and I think I may be having a rouge thread issue. > I hope not since I use synclock in my code when ever a thread is attempting a > write to the database. That seems like the only issue from that page that I > may be doing. I could have up to 30 or more threads reading from the DB but > only one to three active threads writing. The way my code is set up, though > is that each thread would have to wait for the previous thread to finish > writing before its turn to write.
Since you're I/O bound on socket connections, and not CPU or database bound, you might want to just have one database thread that communicates using native inter-thread messaging to pass out work and accept responses from the worker threads. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
