Browse thread
scalable web apps
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: | 2010-07-26 (17:10) |
From: | Sylvain Le Gall <sylvain@l...> |
Subject: | Re: scalable web apps |
On 26-07-2010, Florent Monnier <monnier.florent@gmail.com> wrote: > Le lundi 26 juillet 2010 13:20:46, Dario Teixeira a écrit : >> Hi, >> >> > > How does Ocsigen handle database operations? >> > >> > I thought it was using PG'OCaml, but maybe I'm wrong. >> >> Ocsigen itself does not use PG'OCaml. The two are frequently associated >> because the latest versions of PG'OCaml are Lwt-friendly and therefore >> a good choice for Ocsigen apps. (Note that internally, Ocsigen uses >> either Dbm or Sqlite to store session data). > > 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. Regards, Sylvain Le Gall