On 26-07-2010, Gabriel Kerneis <kerneis@pps.jussieu.fr> wrote:
> On Mon, Jul 26, 2010 at 05:10:01PM +0000, Sylvain Le Gall wrote:
>> > Both Dbm and Sqlite lock the entire files which blocks concurrent uses,
>> > isn't it a problem?
>> 
>> For sqlite, at least, it uses Lwt_preemptive.detach and sqlite3 contains
>> the required caml_enter/leave_blocking_section(s). So Lwt should work
>> without problems with sqlite.
>> 
>> I suppose it is the same for dbm.
>
> No.  For dbm there is a separate daemon (ocsidbm) opening the file once
> and serializing requests sent from and back to Ocsigen through a pipe.
>

Thanks for this clarification. So basically, it also works with Lwt but
using a little bit heavier backend (i.e. launching a process rather than
launching a thread).

Regards,
Sylvain Le Gall