<!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/3.26.0">
</HEAD>
<BODY>
On Fri, 11 Dec 2009 00:17:49 +0000 Tim-Philipp M?ller wrote:<BR>
<BR>
On Thu, 2009-12-10 at 16:08 -0700, Todd Fischer wrote:<BR>
<BR>
Hi,<BR>
<BR>
> Since we are using D-Bus, we need to have a bus name and corresponding<BR>
> object path. I would like to use <BR>
> <BR>
> D-Bus name: org.freedesktop.gstreamer.gstd<BR>
> D-Bus object path: /org/freedesktop/gstreamer/gstd<BR>
<BR>
This is quite a generic part of the namespace you're planning on taking<BR>
over here ('gstd' in the GStreamer domain).<BR>
<BR>
Any reason not to use e.g. /net/sourceforge/harrier/gstd<BR>
or /com/ridgerun/harrier/gstd or somesuch?<BR>
<BR>
As I see it, what you're exposing is basically an API of some sort, and<BR>
just like we wouldn't be keen on seeing third party libraries expose API<BR>
in the GStreamer namespace (not to mention use our domain as origin of<BR>
some sort), I don't think we'd be keen on this for a dbus-based<BR>
interface either.<BR>
<BR>
But maybe that's just me.<BR>
<BR>
Cheers<BR>
-Tim<BR>
<BR>
Tim,<BR>
<BR>
I am trying to take of the world, one name space at a time.<BR>
<BR>
/com/ridgerun/gstreamer/gstd is fine with me - great advertising. If for some reason gstd gets wider adoption, then I will vote against changing it for compatibility reasons. Since we don't have any deployment yet, I figured it was a good time to ask.<BR>
<BR>
Todd<BR>
<BR>
<BR>
</BODY>
</HTML>