[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150422143515.GA23155@dellaz>
Date: Wed, 22 Apr 2015 16:35:15 +0200
From: Michele Curti <michele.curti@...il.com>
To: Havoc Pennington <hp@...ox.com>
Cc: Austin S Hemmelgarn <ahferroin7@...il.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andy Lutomirski <luto@...capital.net>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Arnd Bergmann <arnd@...db.de>,
One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
Tom Gundersen <teg@...m.no>, Jiri Kosina <jkosina@...e.cz>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Daniel Mack <daniel@...que.org>,
David Herrmann <dh.herrmann@...il.com>,
Djalal Harouni <tixxdz@...ndz.org>
Subject: Re: Issues with capability bits and meta-data in kdbus
Hi Havoc.
On Wed, Apr 22, 2015 at 09:27:56AM -0400, Havoc Pennington wrote:
>
> If we say it isn't "general purpose" we could mean more than one thing -
>
> - it's a complete system / batteries-included, with a defined
> protocol, vs. a "make your own protocol" kit
> - it isn't especially appropriate as a cross-machine protocol,
> whether you mean within a cluster or across the internet
> - it isn't portable in a very useful way (it kind of runs on
> windows/mac but isn't the native way of doing things there)
>
> On the other hand, it is "general purpose" in the sense that so many
> apps and services are using it for so many purposes already (i.e. it
> isn't tied to a particular kind of app or service).
>
Just out of curiosity, would you like to change something in dbus design,
if you didn't have to worry about ABI breaks and the like?
Thanks,
Michele
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists