RequestName default flags

[Waldo Bastian]

For the KDE bindings I think I should be using 
DBUS_NAME_FLAG_PROHIBIT_REPLACEMENT in order to get DCOP compatible behavior.

The description for DBUS_REQUEST_NAME_REPLY_IN_QUEUE on  
http://dbus.freedesktop.org/doc/dbus-specification.html#message-bus-names is 
wrong btw, it says

"The name already had an owner, DBUS_NAME_FLAG_REPLACE_EXISTING was not 
specified, and the current owner specified 
DBUS_NAME_FLAG_PROHIBIT_REPLACEMENT."

but it should say

"The name already had an owner, DBUS_NAME_FLAG_REPLACE_EXISTING was  
specified, and the current owner specified 
DBUS_NAME_FLAG_PROHIBIT_REPLACEMENT."

Would it be possible to allow a dash '-' in busnames btw?

Cheers,
Waldo

On Tuesday 02 August 2005 23:05, Havoc Pennington wrote:
> Hi,
>
> For current situation, see:
>
> http://dbus.freedesktop.org/doc/api/html/group__DBusBus.html#ga5
>
> http://dbus.freedesktop.org/doc/dbus-specification.html#message-bus-names
>
>
> I'm not really convinced that the current set of behaviors is right, or
> that the defaults are right.
>
> Which flags are people using and for which use-cases? Ideally we can get
> a lot of followups describing different ways to use D-BUS names and the
> flags people are wanting for them.
>
> It feels to me like the policy for name behavior is in the wrong place,
> since it ends up being hardcoded in both client and server; feels like
> the .service file would make more sense.
>
> Possibly something to fix for 1.0.
>
> Havoc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/dbus/attachments/20050803/e4550174/attachment.pgp