<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/4.6.6"> </HEAD> <BODY> On Fri, 2013-11-15 at 18:45 +0100, Lennart Poettering wrote: <BLOCKQUOTE TYPE=CITE> <PRE> On Fri, 15.11.13 11:21, Ted Gould (<A HREF="mailto:ted@gould.cx">ted@gould.cx</A>) wrote: > One problem we've had is taking arbitrary string (usually application > names) and putting them into object paths on DBus. The characters > allowed in the path is limited, which is fine, but we need some way to > represent the string we're passed through that. libnih has a small > function[1] that does this by taking any character that isn't an ASCII > character or digit and putting it's value as ASCII digits after an > underscore. We've been using this in various places, and I think it'd > be useful if there was an algorithm that was included in the DBus > spec. Why? The spec is something you should follow to stay interoperable, but I don't see how a spec on the precise mappings from some project specific identifiers to bus paths would be needed for that. </PRE> </BLOCKQUOTE> <PRE> </PRE> So that people don't have two mostly similar but slightly incompatible versions of the same thing ;-) <BLOCKQUOTE TYPE=CITE> <PRE> And I am pretty sure that exposing a similar call in a dbus library implementation certainly would make sense but I really don't see why there needs to be a spec about this... </PRE> </BLOCKQUOTE> I more figured that if I went to all the dbus libraries and proposed a patch, they'd say something like: "support a random format you made up, that's silly!" So I'm less worried about it being "in the spec" and more about it being agreed upon as the way to do things. I think that a recommendation in the spec is probably the best place to put that for future implementors. Ted </BODY> </HTML>