Re: trunk r116456: Improve dbus performance on synchronous calls

[Daniel Colascione]

On 02/17/2014 01:08 PM, Michael Albinus wrote:
> address@hidden writes:
>
> > > > Why `push'? It adds the event on top of `unread-command-events',
> > > > changing the event order when there are already events in that list.
> > >
> > > Hrm. I was getting it from sit-for:
> >
> > Nope. You're right: fixed. Thanks for pointing that out.
>
> Maybe `sit-for' is wrong then as well? I haven't checked ever (and
> situations, where `unread-command-events' contains more than one event
> seem to be rare).

sit-for is right: it's reading one event, then immediately sticking it 
back on the queue. Push is exactly the right operation there.