tree f78e9964402022d5469d1d1bbf81c365350481da
parent 0283f7cb6b91fb87bad6d4ae1c312b31559bb85a
author Brad Bishop <bradleyb@fuzziesquirrel.com> 1604941052 -0500
committer Brad Bishop <bradleyb@fuzziesquirrel.com> 1606843372 -0500

main: refactor service initialization

The service initialization tasks currently consist of:
- Instantiating freedesktop.ObjectManager
- Instantiating an updater instance and providing it with a dbus
  connection
- Instantiating a watch instance and attaching it to the program event
  loop
- Claiming a well known name on DBus

Move these service initialization tasks to a new function.  This opens
the door to _not_ performing service initialization in an easy to read
way.

A couple of subtle ordering changes have occurred:
- The bus socket callbacks are attached to the event loop as soon as the
  event loop is instantiated.  This change doesn't have any functional
  impact; any data waiting in the dbus socket isn't processed until
  loop.loop() is called anyway.  What the relocation does enable is access
  to the event loop in the new method, via the of the bus.get_event()
  method.
- watch is now instantiated prior to claiming a busname.  That's ok
  because that doesn't result in any observable difference to client
  applications that may be watching for signals.

Change-Id: Ie0a42eb5764114110056cac2ad74da651c8dbd90
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>