Hi Thiago Macieira:<br>
<br>
thank you for your so quick reply.<br>
<br>
I think I understand the question.<br>
<br>
And we think queued messages function is very useful and valueble.<br>
<br>
Because it is more simple for developer : do not need write the .service file<br>
<br>
Also this function will not make bad the performance of dbus deamon,<br>
<br>
for example after a certain time (30 seconds), deamon will delete the queued <br>
messages.<br>
<br>
Is it difficult to implement it?<br>
<br>
<br><br>On 1/25/07, Thiago Macieira <<a href="mailto:thiago@kde.org">thiago@kde.org</a>> wrote:<br>> anlong sun wrote:<br>> >When dbus daemon does not have the .service file, the dbus message will<br>> > not be queued if dbus daemon fail to launch application B.
<br>> <br>> That is correct. That is the intended behaviour.<br>> <br>> If the target application cannot be launched, then the message cannot be<br>> processed. The caller application will receive an error back.
<br>> <br>> >How can I do that : launch B application by myself instead of by dbus<br>> >daemon and still queued the message which can be gotten by B after<br>> >launched?<br>> <br>> You cannot. There is no such thing as queued messages. Either the target
<br>> service name exists at the time the message is received by dbus-daemon,<br>> or the daemon knows how to start the service.<br>> <br>> --<br>> Thiago Macieira - thiago (AT) <a href="http://macieira.info">
macieira.info</a> - thiago (AT) <a href="http://kde.org">kde.org</a><br>> PGP/GPG: 0x6EF45358; fingerprint:<br>> E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358<br>> <br>> <br>> <br>