Sugar architecture review 1

Presence service

• Turn the presence service in a DBUS service, to simplify the code and decrease network usage.
• Fix the misuse of zeroconf service types.
• Define an API that makes straight forward the most common case: activity specific service browing.

Activities

• It should not be necessary to write a Shell per each activity to manage multiple activities in the same process.
• Abstract activity construction.
• Define the status of modules like Presence service, the one-to-one chat listener, Voip services, bots. They are definately not activity because they are not user visible and they are global services. (My current thinking is to define those as parts of the shell or anyway shell extensions).