Il giorno lun, 21/03/2011 alle 12.45 -0400, David Zeuthen ha scritto: > Hi, > > On Sun, Mar 20, 2011 at 4:25 PM, Jasper St. Pierre > <jstpierre mecheye net> wrote: > > Additionally, take a look at the evolution of the patches that davidz > > did, he had two or three different event sources that are now all > > gone, and those might be useful to start from. > > Right. And if we want to support multiple different calendar servers > (and that's a big 'if' I think...), then it should be done in a way so > the code for interacting with the calendar server is _out of process_ > like it currently is for e-d-s. Anything else (such as relying on a > native library in-process) is going to be too risky... we simply > cannot trust that the native library is going to do the right thing > and not block etc... (at least the e-d-s- libraries didn't). See > https://bugzilla.gnome.org/show_bug.cgi?id=641396 for more discussion. So this calendar-server stuff is not a temporary HACK and gnome-shell will have a daemon running at all time for the calendar (even if evolution is not used)? I thought it would be removed when e-d-s supported async calls. Native libraries are there for a reason. It would be as if we avoid using telepathy-glib, upower-glib or libnm-glib, fearing they could block or have bugs. Giovanni
Attachment:
signature.asc
Description: This is a digitally signed message part