Starting the kdbus discussions

[Ted Gould]

On Wed, 2014-01-08 at 11:15 -0800, Marcel Holtmann wrote:

+AD4 let me give a simple analogy here. You are also not sending HTTP
+AD4 headers along with your TCP/IP socket. So neither should kdbus require
+AD4 any extra metadata that is not needed to transport payload. At the end
+AD4 of the day kdbus is a routing protocol to move messages from process A
+AD4 to process B. It needs enough information to do exactly this and
+AD4 nothing more.


I think that aligns with the naming issue that Greg pointed out.  What
would be expected from something called +ACI-kdbus+ACI would be different than
something called +ACI-kgenericbus+ACI.  Likewise if the kernel module was
+ACI-khttp+ACI you'd expect a different relationship between headers and
payload than in +ACI-ktcp+ACI.

So, it seems to me that there are a lot of confusion created by the
language being used.  My current understanding is that +ACI-kdbus+ACI is
designed to be a generic bus functionality in the kernel.  Systemd then
implements a dbus-like (perhaps dbus v2) protocol over that generic bus
functionality.  In theory, other buses could use that same generic
functionality if they so choose.  So what Lennart started this thread
with is to add to the DBus spec +ACI-How to represent DBus on kdbus+ACI just
like the current spec is +ACI-How to represent DBus over sockets.+ACI  Please
correct me if I'm wrong.

Ted

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http:+AC8ALw-lists.freedesktop.org+AC8-archives+AC8-dbus+AC8-attachments+AC8-20140109+AC8-ce9e7a30+AC8-attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application+AC8-pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http:+AC8ALw-lists.freedesktop.org+AC8-archives+AC8-dbus+AC8-attachments+AC8-20140109+AC8-ce9e7a30+AC8-attachment.pgp>