KIO protocols namespace
coolo at kde.org
Mon Dec 9 08:05:44 GMT 2002
Am Montag, 9. Dezember 2002 01:57 schrieb Germain Garand:
> Le Dimanche 08 Décembre 2002 22:36, David Faure a écrit :
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > On Sunday 08 December 2002 22:30, Germain Garand wrote:
> > > > > My real question is : wouldn't it be a good thing to have a central
> > > > > place were authors of kio-slaves, wether they are third-party or
> > > > > part of KDE, could "register" a namespace for their slaves ?
> > This "problem" extends to binary names, then. Your point is "what if two
> > people write a kmymp3collection" ? But even then, it's not specific to
> > KDE. What if two people write a /usr/bin/mp3collectionsorter? Do we need
> > a global opensource-program registry? Bah.
> mmhh... difference is you can install your binaries in different locations
> and still have them coexist peacefully, getting the right thing up through
> fully qualified pathes.
> Here, protocols are KDE wide. If the name is taken, you are simply out of
> Likewise, isn't it the whole point of internet names registration to keep
> unique resources from endless disputes and conflicts ?
> I wonder if it's not a better analogy... 8)
Well, if you want to avoid clashes, avoid short names. If you had named
the protocol just one letter longer you had decreased the chances of a
conflict by factor 26! Now imagine how low the chances would be for
I'd say: KDE's namespace repository is kde-devel at kde.org and lists.kde.org.
If you'd announced the protocol there (perhaps you even did :), you could
have an argument why the new developer needs to rename his.
More information about the kde-core-devel