On Friday, February 21, 2014 08:30:02 Kevin Ottens wrote:
> Hello,
>
> On Thursday 20 February 2014 20:03:20 Aaron J. Seigo wrote:
> > I ran into an interesting situation the other day with libkactivities: it
> > uses KDBusConnectionPool to create connections in a thread-safe manner.
> > KDBusConn
On Friday, 2014-02-21, 08:30:02, Kevin Ottens wrote:
> Hello,
>
> On Thursday 20 February 2014 20:03:20 Aaron J. Seigo wrote:
> > I ran into an interesting situation the other day with libkactivities: it
> > uses KDBusConnectionPool to create connections in a thread-safe manner.
> > KDBusConnectio
Hello,
On Thursday 20 February 2014 20:03:20 Aaron J. Seigo wrote:
> I ran into an interesting situation the other day with libkactivities: it
> uses KDBusConnectionPool to create connections in a thread-safe manner.
> KDBusConnectionPool creates a connection in whatever thread it happens to
> be
On Thu, February 20, 2014 20:03:20 Aaron J. Seigo wrote:
> Either a better solution needs to be found for KDBusConnectionPool or a
> warning should be placed prominently in the apidox about this “gotcha” and
> perhaps it should be completely avoided in other frameworks where it is
> impossible to k
Hi..
I ran into an interesting situation the other day with libkactivities: it uses
KDBusConnectionPool to create connections in a thread-safe manner.
KDBusConnectionPool creates a connection in whatever thread it happens to be
executed from. In libkactivities this creates a problem as a single
