Currently when we register a GATT application hierarchy by using GattManager1->RegisterApplication, BlueZ reads the entire set of attributes in one go. After that if we change the attributes, BlueZ will continue to serve only the original set of attributes. This is because BlueZ isn't currently listening to the InterfaceAdded and InterfaceRemoved signals from the object manager that is managing the attributes in the application.

BlueZ needs to listen for these signals and update its GATT database accordingly.

Even though this isn't critical, we really want this. Every time we register an application which registers more than one service, we can end up having a new call to RegisterApplication with an increasing number of services. This isn't a state we want to stay in for any longer than the minimum possible.