Since the server is one process there is no need for Sqlite to use its sync capability derived for multiple processes and you can KISS by wrapping Sqlite in your own synhronization.
The nice feature of a threaded application server using embedded Sqlite is that there is no interprocess communication. We use sendfile/TransmitFile for the network traffic and keep a pool of active threads so honoring a database access is fast and efficient, especially if the database is kept open and you save prepared statements. JS Marcus Grimm wrote: > John, > > thanks for the reply. > > you mean you do the synchronization by your selve rather > than let it do sqlite internally ? > > Marcus > > John Stanton wrote: > >>We have been using such a server embadding Sqlite for some time with >>success. We actually use pthreads exclusive and read only mutexes for >>synchronization since all Sqlite access is threaded in the one process. >>JS >> _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
