new dbus api coalesces state change

[Sam Leffler]

The coalescing of PropertiesChanged signals is great but doing this for
State's means the client has to infer missing states.  Unfortunately the way
things are implemented it's not simple to just flush a pending signal in the
lowest level of the dbus code where it's easy to recognize this as the state
has already been changed.  Any suggestions on how to handle this?  Or is it
expected the client will just infer all the missing state transitions? (can
be hard and lead to problems)

-Sam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20100819/1328f8f2/attachment.htm