Hello all, One oft-cited method to address SQLite's limited concurrency support is to use a client-server database. Such databases enjoy better concurrency thanks to their use of a master, coordinating process which is hard to obtain efficiently using unrelated processes like those of SQLite. What's the key to this master process's increased concurrency that is difficult to emulate using a scheme among unrelated processes? Does the primary benefit of the master process lie in its ability to efficiently detect abnormal termination of child processes and deal with their locks?
Regards, Iker -- Iker Arizmendi AT&T Labs - Research Speech and Image Processing Lab w: http://research.att.com _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
