REF add note
This commit is contained in:
parent
d9b1886db6
commit
80c3d33010
|
@ -112,10 +112,16 @@ withDBusClientConnection cb n logfile f =
|
||||||
env <- mkSimpleApp lf Nothing
|
env <- mkSimpleApp lf Nothing
|
||||||
runRIO env $ displayMaybe' cb f =<< getDBusClient n
|
runRIO env $ displayMaybe' cb f =<< getDBusClient n
|
||||||
|
|
||||||
-- | Run a plugin action with a new DBus client and logfile path.
|
-- | Run a plugin action with a new DBus client and logfile path. This is
|
||||||
-- This is necessary for DBus callbacks which run in separate threads, which
|
-- necessary for DBus callbacks which run in separate threads, which will
|
||||||
-- will usually fire when the parent thread already exited and killed off its
|
-- usually fire when the parent thread already exited and killed off its DBus
|
||||||
-- DBus connection and closed its logfile.
|
-- connection and closed its logfile. NOTE: unlike 'withDBusClientConnection'
|
||||||
|
-- this function will open and new logfile and client connection and close both
|
||||||
|
-- on completion. 'withDBusClientConnection' will only close the log file but
|
||||||
|
-- keep the client connection active upon termination; this client will only be
|
||||||
|
-- killed when the entire process is killed. This distinction is important
|
||||||
|
-- because callbacks only need ephemeral connections, while listeners (started
|
||||||
|
-- with 'withDBusClientConnection') need long-lasting connections.
|
||||||
withNestedDBusClientConnection
|
withNestedDBusClientConnection
|
||||||
:: (MonadUnliftIO m, SafeClient c, MonadReader (PluginEnv s c) m)
|
:: (MonadUnliftIO m, SafeClient c, MonadReader (PluginEnv s c) m)
|
||||||
=> Maybe BusName
|
=> Maybe BusName
|
||||||
|
|
Loading…
Reference in New Issue