Re: [Evolution] Re: Shareing a calendar

[Christian Borup <borup borup com>]

On s?, 2003-06-08 at 10:29, Martin Skjöldebrand wrote:
> tis 2003-06-10 klockan 05.56 skrev Martin Skjöldebrand:
> > I want to share a calendar between two users on my box.
> > Running 1.3.92 I've failed to get it to work, and the mail archives
> are
> > empty on the subject.
> >
> > I've put the Calendar folder form ~/evolution/local/ on /opt2 and made
> a
> > link to the original folder (renaming the original folder). This I did
> > on both accounts making sure that /opt2/evolution/local/Calendar is
> > chmoded 777. 
> >
> > Still anything entered in one account is not viewable on the other
> > account. What is going on here? Anyone with any success stories?
>
> Apparently it *does* work, kind of.
> I noticed this when I rebooted my computer, and the calendar info was
> seen - something apparently has to be restarted for this to work as
> intended.

You got lucky... You could just as well have ended up with a corrupt
file.

Wombat, the calendar backend of evolution, is not designed to
have more than one process accessing the calendar file. In fact the
Wombat is designed to be that one process that does all the accessing of
the calendar file, no matter how many frontends are running (the
frontends will mostly be evolution itself and multisync).

The Wombat keeps all the entries in the calendar in memory, only syncing
changes to disk once in a while (possibly only on shutdown - I haven't
checked). 

> Anyone with info on what, and how to do it automagically?

Well, you are doing something that the wombat was not designed for. So
it will never be pretty. After each update you would have to shut down
both wombats making sure that the one with the most up to date calendar
is shutdown last.

The Wombat needs to be the only process accessing the file. In principle
it should be easy to register the Wombat for user one with the oafd
(bonobo-activation?) of user two, thus having the Wombat do what it does
best, ie serialising the accesses on several clients to the one file.
However, I don't think anybody has done it, and I'm not even sure it
oafd will let you do it.

There has been a lot of talk about allowing the Wombat to read .ical
files from a http (webdav) server. While it may sound difficult it
really shouldn't be, so it may actually be easier to get going than the
above solution.

./borup