More follow_name_owner_changed optimiztion

* reasoning changed from a FIXME to a NOTE to explain why we need
     to follow_name_owner_changed
This commit is contained in:
John (J5) Palmieri
2007-08-24 18:25:56 -04:00
parent 628fe7b5da
commit 2cae66b0ea
3 changed files with 21 additions and 6 deletions
+5 -4
View File
@@ -50,10 +50,11 @@ class ActivityRegistry(gobject.GObject):
bus = dbus.SessionBus()
# FIXME: Is follow_name_owner_changes what we really want?
# It speeds up the start time by about 2 seconds
# but is really a side effect of starting a proxy
# in this state (i.e. we don't block in the constructor)
# NOTE: We need to follow_name_owner_changes here
# because we can not connect to a signal unless
# we follow the changes or we start the service
# before we connect. Starting the service here
# causes a major bottleneck during startup
bus_object = bus.get_object(_ACTIVITY_REGISTRY_SERVICE_NAME,
_ACTIVITY_REGISTRY_PATH,
follow_name_owner_changes = True)