[Bug 29811] A way for client application to request minimum presence on the account

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=29811

--- Comment #2 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2010-09-01 06:21:00 PDT ---
This looks good to merge as a draft soon: today, if you fix the terminology.

-------------------------------------

Merge blocker:

Request is a name that's highly likely to collide, causing problems for things
like dbus-python; also, in Telepathy, Request usually means "this blocks". It
should be should be AddMinimumStatus or something. Likewise for Requests ->
MinimumStatusRequests and Release -> RemoveMinimumStatus (my suggested names
only, if you have better ones I'd like to hear them).

--------------------------------------

Undraft blockers:

The introduction should describe the data model: each client's unique name may
set a minimum desired status, and the actual status will be the maximum chosen
from the set (RequestedPresence + all clients' minima).

If it makes sense for the minimum status to contain a user-defined message, I'm
ambivalent about AddMinimumStatus(u, s, s) vs. AddMinimumStatus((uss)). I'm not
at all sure that it makes sense, though: if it doesn't, we could use (u, s) and
say that the user-defined message comes from the RequestedPresence?

Perhaps it would be worth saying that AddMinimumStatus((Offline, "offline",
"")) is exactly equivalent to RemoveMinimumStatus(), and results in the client
being removed from the map? If so, we could even drop RemoveMinimumStatus()
altogether.

Under what circumstances can Request raise NotAvailable?

Does Requests have change notification? If it doesn't, you should explicitly
say so, with rationale (in this case, "because the property only exists to
illustrate how the interface works" would be suitable rationale :-)

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.