On Thu, Mar 22, 2018 at 01:10:14PM +0100, Pavel Hrdina wrote:
> On Wed, Mar 21, 2018 at 02:21:05PM +, Daniel P. Berrangé wrote:
> > On Wed, Mar 21, 2018 at 11:02:43AM +0100, Pavel Hrdina wrote:
> > > We will switch to GDBus implementation of D-Bus protocol because
> > > sd-bus implementation
On Wed, Mar 21, 2018 at 02:21:05PM +, Daniel P. Berrangé wrote:
> On Wed, Mar 21, 2018 at 11:02:43AM +0100, Pavel Hrdina wrote:
> > We will switch to GDBus implementation of D-Bus protocol because
> > sd-bus implementation is not thread safe.
> >
> > Processing messages in threads is
On Wed, Mar 21, 2018 at 02:21:05PM +, Daniel P. Berrangé wrote:
> On Wed, Mar 21, 2018 at 11:02:43AM +0100, Pavel Hrdina wrote:
> > We will switch to GDBus implementation of D-Bus protocol because
> > sd-bus implementation is not thread safe.
> >
> > Processing messages in threads is
On Wed, Mar 21, 2018 at 11:02:43AM +0100, Pavel Hrdina wrote:
> We will switch to GDBus implementation of D-Bus protocol because
> sd-bus implementation is not thread safe.
>
> Processing messages in threads is essential since Libvirt API can
> take some significant amount of time to return and
We will switch to GDBus implementation of D-Bus protocol because
sd-bus implementation is not thread safe.
Processing messages in threads is essential since Libvirt API can
take some significant amount of time to return and that would block
the whole libvirt-dbus daemon.
Signed-off-by: Pavel