Re: [Evolution-hackers] Overview of camel-lite

2007-06-11 Thread Gilles Dartiguelongue
Le lundi 11 juin 2007 à 10:57 +0300, Philip Van Hoof a écrit : * All compilation warnings fixed (we usually compile with -Wall and -Werror). Fixing this caused four major bug fixes in initialisation of variables in Camel. ok, right away, let me just say evo team is interested in

Re: [Evolution-hackers] Overview of camel-lite

2007-06-11 Thread Philip Van Hoof
On Mon, 2007-06-11 at 10:54 +0200, Gilles Dartiguelongue wrote: Le lundi 11 juin 2007 à 10:57 +0300, Philip Van Hoof a écrit : * All compilation warnings fixed (we usually compile with -Wall and -Werror). Fixing this caused four major bug fixes in initialisation of variables in

Re: [Evolution-hackers] Overview of camel-lite

2007-06-11 Thread Srinivasa Ragavan
On Mon, 2007-06-11 at 12:47 +0300, Philip Van Hoof wrote: On Mon, 2007-06-11 at 14:48 +0530, Srinivasa Ragavan wrote: On Mon, 2007-06-11 at 10:57 +0300, Philip Van Hoof wrote: I'm going to make an overview of camel-lite so that if people read the discussions here, that they know what it's

Re: [Evolution-hackers] Introduction and Questions

2007-06-11 Thread Ross Boylan
I'm preserving the exchange for context; my responses are sprinkled below. On Sun, 2007-06-10 at 23:47 -0400, Jeffrey Stedfast wrote: On Sun, 2007-06-10 at 15:55 -0700, Ross Boylan wrote: On Fri, 2007-06-08 at 20:22 -0400, Jeffrey Stedfast wrote: Second question: even if it creates a

Re: [Evolution-hackers] Introduction and Questions

2007-06-11 Thread Ross Boylan
On Mon, 2007-06-11 at 09:46 -0700, Ross Boylan wrote: Speaking of complexity, evolution/camel (and maybe Gnome?) do a kind of objects with C. Why not just use C++? Was the C++ toolchain too unreliable at the start, or was there some other reason? I didn't mean to exclude other alternatives.

[Evolution-hackers] Camel Data Cache mechanism

2007-06-11 Thread Sebastien Tandel
Hi, I am looking at the way CAMEL is working and have some questions about the cache implementation. First, let's see if I've understood the mechanism basics (and, of course, don't hesitate to correct me if I'm wrong :)) Camel has a generic cache system which stores objects in Camel Bags.

Re: [Evolution-hackers] Introduction and Questions

2007-06-11 Thread Jeffrey Stedfast
On Mon, 2007-06-11 at 09:46 -0700, Ross Boylan wrote: I'm preserving the exchange for context; my responses are sprinkled below. On Sun, 2007-06-10 at 23:47 -0400, Jeffrey Stedfast wrote: On Sun, 2007-06-10 at 15:55 -0700, Ross Boylan wrote: On Fri, 2007-06-08 at 20:22 -0400, Jeffrey

Re: [Evolution-hackers] Camel Data Cache mechanism

2007-06-11 Thread Jeffrey Stedfast
On Mon, 2007-06-11 at 15:27 -0300, Sebastien Tandel wrote: Hi, I am looking at the way CAMEL is working and have some questions about the cache implementation. First, let's see if I've understood the mechanism basics (and, of course, don't hesitate to correct me if I'm wrong :))

Re: [Evolution-hackers] Introduction and Questions

2007-06-11 Thread Ross Boylan
On Mon, 2007-06-11 at 14:39 -0400, Jeffrey Stedfast wrote: So it sounds as if Camel could (in principle) respond to a move request by issuing the appropriate IMAP command and then, starting a thread to do the other activities (indexing the target folder and deleting the the