On Thu, Sep 24, 2009 at 10:14:58AM -0300, Luiz Capitulino wrote: > On Thu, 24 Sep 2009 16:07:28 +0300 > Avi Kivity <a...@redhat.com> wrote: > > > On 09/24/2009 04:05 PM, Luiz Capitulino wrote: > > >>> I think the easiest way to have this would be to add a > > >>> monitor command to disable capabilities. Like a command to > > >>> disable async messages. > > >>> > > >>> > > >> Other way around, enable things that you want. > > >> > > > Ok, I will add support for this in my tree then, async messages > > > will be considered a capability. > > > > > > > Actually, if async messages are specified from day one they can be > > always active. The client can easily ignore them. > > That's also fine by me, but we were talking about having a > command to disable async messages... If we do this, I would > prefer to make it a capability instead, this way it can use > the same infrastructure (as opposed to special treatment).
Maybe per message type (error/warning/info/debug). -- MST
