On 08/12/2015 01:46 PM, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> Create a seperate pending event structure MonitorQAPIEventPending.
s/seperate/separate/
> Use a MonitorQAPIEventDelay callback to handle the delaying. This
> allows other implementations of throttling.
>
>
On 08/12/2015 02:00 PM, Laszlo Ersek wrote:
> Assume there has been a long period of silence (no attempts to emit an
> event). Now some client code makes a call to emit the event.
>
> Will that event be emitted immediately, or will it be delayed to see if
> more are coming? I'd like to understand
Hi
- Original Message -
> On 08/12/15 21:46, marcandre.lur...@redhat.com wrote:
> > From: Marc-André Lureau
> >
> > Create a seperate pending event structure MonitorQAPIEventPending.
> > Use a MonitorQAPIEventDelay callback to handle the delaying. This
> > allows other implementations of
On 08/12/15 21:46, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> Create a seperate pending event structure MonitorQAPIEventPending.
> Use a MonitorQAPIEventDelay callback to handle the delaying. This
> allows other implementations of throttling.
>
> Signed-off-by: Marc-André L
From: Marc-André Lureau
Create a seperate pending event structure MonitorQAPIEventPending.
Use a MonitorQAPIEventDelay callback to handle the delaying. This
allows other implementations of throttling.
Signed-off-by: Marc-André Lureau
---
monitor.c| 124 +
