On Mon, Feb 04, 2013 at 13:51:49 +, Daniel P. Berrange wrote:
> On Mon, Feb 04, 2013 at 02:51:19PM +0100, Jiri Denemark wrote:
> > On Mon, Feb 04, 2013 at 14:01:27 +0100, Jiri Denemark wrote:
> > > On Fri, Feb 01, 2013 at 11:18:25 +, Daniel P. Berrange wrote:
> > > > From: "Daniel P. Berran
On Mon, Feb 04, 2013 at 02:51:19PM +0100, Jiri Denemark wrote:
> On Mon, Feb 04, 2013 at 14:01:27 +0100, Jiri Denemark wrote:
> > On Fri, Feb 01, 2013 at 11:18:25 +, Daniel P. Berrange wrote:
> > > From: "Daniel P. Berrange"
> > >
> > > As a step towards making virDomainObjList thread-safe tu
On Mon, Feb 04, 2013 at 14:01:27 +0100, Jiri Denemark wrote:
> On Fri, Feb 01, 2013 at 11:18:25 +, Daniel P. Berrange wrote:
> > From: "Daniel P. Berrange"
> >
> > As a step towards making virDomainObjList thread-safe turn it
> > into an opaque virObject, preventing any direct access to its
>
On Fri, Feb 01, 2013 at 11:18:25 +, Daniel P. Berrange wrote:
> From: "Daniel P. Berrange"
>
> As a step towards making virDomainObjList thread-safe turn it
> into an opaque virObject, preventing any direct access to its
> internals.
>
> As part of this a new method virDomainObjListForEach i
From: "Daniel P. Berrange"
As a step towards making virDomainObjList thread-safe turn it
into an opaque virObject, preventing any direct access to its
internals.
As part of this a new method virDomainObjListForEach is
introduced to replace all existing usage of virHashForEach
---
src/conf/domai