Suppose I am writing a new calendar backend. Which of these two
interfaces is preferred? If I implement ECalBackendSync, will
operations on the calendar cause the UI to block?
Thanks!
Peter
___
Evolution-hackers mailing list
Evolution-hackers@gnome.org
On Mon, 2006-07-31 at 03:08 -0400, Peter Colijn wrote:
Suppose I am writing a new calendar backend. Which of these two
interfaces is preferred?
The requirements of your application and the characteristics of your
backend should guide the choice.
If I implement ECalBackendSync, will
Hi peter,
You would need to implement both. The ECalBackendSync class has a
sync lock, which is used if the backend can handle only one operation at
a time. It provides the results immediately to the caller.
ECalBackend class provides notifications to the client from EDS.
Please go through
Hi Chenthill,
On 7/31/06, chenthill [EMAIL PROTECTED] wrote:
You would need to implement both. The ECalBackendSync class has a
sync lock, which is used if the backend can handle only one operation at
a time. It provides the results immediately to the caller.
ECalBackend class provides
Are you writing a new backend similar to file/http/groupwise ? If so you
can implement the virtual methods extending from ECalBackendSync class.
You can prolly refer to any of the existing backends or
evolution-exchange/calendar.
thanks, Chenthill.
On Mon, 2006-07-31 at 04:22 -0400, Peter Colijn
During the 2.6.x cycle, there were version bumps of libecal and
libedata-cal to make up for a previous ABI break in these two
libraries. It was unfortunate to bump the versions in a stable tree,
but now I'm more interested in the 2.8.x release.
When the version bump was commited to 2.6.x, it was
