Annotation type for an asyncronous method using dbus qt3 binding

[Thiago Macieira]

Havoc Pennington wrote:
>The NO_REPLY flag is a property of the specific invocation (or of code
>generated by a binding), not a property of the interface per se. That
>is, NO_REPLY is an aspect of how a method is invoked, not an aspect of
>the method.
>
>(Hopefully this is what that annotation does in Qt also, otherwise I
>don't think stuff marked with it will be interoperable)

When generating proxy interfaces, if the flag is set, the DBusMessage 
containing the call with set the NO_REPLY flag. The caller will also not 
block and will return immediately after posting the message.

When generating server (adaptor) interfaces, if the flag is set, it 
imposes a void return type (and no out parameters). 

The glue around the function being called to handle calls will always send 
a reply if the NO_REPLY flag isn't set, and will always not send one if 
the flag is set. That doesn't mean that the functions called don't send 
replies of their own.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.freedesktop.org/archives/dbus/attachments/20071106/10f0dfe4/attachment.pgp