end of a dbus signal message

[John (J5) Palmieri]

I'm not sure if I understand what you are doing.  You are basically
piping dbus-monitor and scraping the output?  There is no guarantee it
will stay the same between releases.  I would suggest either writting
tcl bindings or writing a small C app that formats the signals the way
you would like them.  Using dbus-monitor also wastes resources as it
gets all the messages sent from the bus (excluding those which it does
not have privilege to in the case of the system bus).


On Tue, 2005-10-18 at 16:27 +0200, pan wrote:
> Dear dbus experts,
> 
> I'm writing a dbus monitor for a chat client (aMSN) in tcl.
> Do this by opening a pipe to "unbuffer dbus-monitor --session/system".
> Below are two example signals I sometimes receive. And the main reason why
> I made this plugin (to know I received new mail by a nice notification
> popup).
> 
> My question is, is a dbus signal always two lines?
> Is it always true that there is one header line\n and one body line\n ?
> Maybe I overlooked this in the specification, couldn't easily find it and
> someone told me it was not always two lines.
> If that true, how can the end of a message be detected?
> 
> Thanks for your help.
> 
> 
> signal sender=:1.270 -> dest=(null destination)
> interface=org.gnome.evolution.mail.dbus.Signal; member=Newmail
>  0 string "imap://jonne@imap.isa.ewi.tudelft.nl/Sent%20Items"
> 
> interface=org.gnome.evolution.mail.dbus.Signal; member=MessageReading
>  0 string "INBOX"
> 
> 
> _______________________________________________
> dbus mailing list
> dbus at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dbus
--