Ticket #5032 (new defect)
Presence service Activity.joined property
| Reported by: | rwh | Owned by: | Collabora |
|---|---|---|---|
| Priority: | normal | Milestone: | Future Release |
| Component: | presence-service | Version: | |
| Keywords: | Cc: | marco, tomeu, morgs | |
| Action Needed: | Verified: | no | |
| Deployments affected: | Blocked By: | ||
| Blocking: |
Description
Hi,
I think there is an issue with the presence service Activity.joined property. This property is nicely maintained by the presence service (as far as I can tell), and in the client wrapper implementation it is also tracked. The client wrapper emits a joined signal after join() is called on that object and you are actually joined. Now the annoying thing is that this signal belongs to the GObject, and different instances of the wrapper will not all see the signal. It would be nicer in this join was implemented as a DBus signal so that all instances would see it. Now it is hard for the shell (e.g. connect()ing to the join signal has no effect) to tell whether the owner joins (or leaves), although we could probably use the buddy-joined and buddy-left signals and see if is about the owner.
