You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Processes can use D-Bus protocol to talk directly to each other, without a bus.
But in the current code DBusServerBase's __init__ (and then all of its subclasses) has "bus type" and "name" parameters that both don't exist in server/peer-to-peer mode.
The text was updated successfully, but these errors were encountered:
amezin
changed the title
Support server mode
Support server/peer-to-peer mode
Jul 12, 2021
Does jeepney support this? I don't think so, right?
No, it does. At least, from the code it looks so.
class DBusConnection:
...
def __init__(self, reader: asyncio.StreamReader, writer: asyncio.StreamWriter)
jeepney's asyncio.DBusConnection can be created from an arbitrary reader/writer pair (and, luckily, it also skips typical bus connection steps). So I can create it from any socket/pipe I want.
What's the point of storing bus and name?
By the way, acquiring a (well-known) bus name isn't necessary for exporting objects, even when connecting to a bus (they will be available under connection's unique name).
See https://developer.gnome.org/gio/stable/GDBusServer.html
Processes can use D-Bus protocol to talk directly to each other, without a bus.
But in the current code
DBusServerBase
's__init__
(and then all of its subclasses) has "bus type" and "name" parameters that both don't exist in server/peer-to-peer mode.The text was updated successfully, but these errors were encountered: