Re: [Evolution-hackers] Camel Manifesto (update)

2011-03-13 Thread Matthew Barnes
On Sun, 2011-03-13 at 21:32 +, David Woodhouse wrote: > Ug, and now I've found that that workaround doesn't work either. If we > try to rename a folder, we end up blocking in the main thread, waiting > for the soup request that we deliberately put into an idle function so > that it could run i

Re: [Evolution-hackers] Camel Manifesto (update)

2011-03-13 Thread David Woodhouse
On Thu, 2011-02-17 at 18:37 +, David Woodhouse wrote: > I was told today that the GIO (and libsoup) async methods may not be > called from a thread other than the one running the mainloop. I found a > stupid race in libsoupĀ¹ and filed a fix, but the bug was closed INVALID > because apparently i

Re: [Evolution-hackers] Camel Manifesto (update)

2011-02-17 Thread Matthew Barnes
On Thu, 2011-02-17 at 18:37 +, David Woodhouse wrote: > I assume that your intention is that the Camel async methods would *not* > be similarly broken, and that you should be able to call them from *any* > thread and expect them not to break? > > If so, we need be *very* careful about calling

Re: [Evolution-hackers] Camel Manifesto (update)

2011-02-17 Thread David Woodhouse
On Mon, 2010-09-27 at 12:52 -0400, Matthew Barnes wrote: > 3. Asynchronous Methods > --- > > All the upgrades I've been making to Camel over the past year, and all > the changes described above were in preparation for this: Camel now has > an asynchronous public API. > > Let m

Re: [Evolution-hackers] Camel Manifesto (update)

2010-09-29 Thread Milan Crha
On Mon, 2010-09-27 at 12:52 -0400, Matthew Barnes wrote: > Transient operations are now implicit: if you push a new status > message onto a non-empty message stack, the message is treated as > transient. A transient message just means there's a longer delay > before the message is shown in Evoluti

Re: [Evolution-hackers] Camel Manifesto (update)

2010-09-27 Thread Matthew Barnes
Here's another update on how the Camel API upgrades are coming along. My initial roadmap from 2009 is referenced in [1], and my last update was in May [2]. This next round of API changes will be fairly disruptive, so I'd like to coordinate with anyone finishing up their own Camel branch so my chan

Re: [Evolution-hackers] Camel Manifesto (update)

2010-05-08 Thread Matthew Barnes
I wanted to give a status update on how this is progressing, since some of you may have noticed me breaking Camel's API with gleeful abandon since the 2.31 development cycle began. My initial roadmap is here: http://mail.gnome.org/archives/evolution-hackers/2009-November/msg00019.html What's Acc