Hi,
Personally, I think relying on asynchronous events to provide
reliable
status is a bad idea. Management connections can and will get
disconnected, buffers will get filled and event notifications will be
dropped.
I somehow like the idea from someone (Jamie?) somewhere in this thread
to model the notification like unix signals. Just flag that something
changed. Don't carry the actual info, just ping the management app,
which in turn must use "info <whatever>" to get the details.
That solves the queuing issue. I also closes the command vs.
notification races. Management apps don't need new parsers, the
existing "info <foo>" parser(s) will do just fine.
cheers,
Gerd