Re: glib: processing events in multiple threads

On Tue, 2013-04-30 at 10:42 +0200, Patrick Ohly wrote:

In SyncEvolution, I am using a library with synchronous method calls
which is unaware of glib.


Just for the record, there's one more angle to this: EDS' libebook and
libecal offer synchronous versions of all API calls, which is very
useful for apps which are non-interactive (command line tools), have a
simple logic (unit tests) or use their own kind of event loop +

The only problem is that in the current implementation, EDS makes the
implicit assumption that there is a thread running a glib event loop
with the default context (as suggested in this mail thread). That
assumption is not documented and might not be true; I'm trying to
understand whether that dependency on the process environment can be

Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]