[Bug 27752] Deficiencies in Location setting API

[bugzilla-daemon at freedesktop.org]

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

Simon McVittie <simon.mcvittie at collabora.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Status Whiteboard|                            |specmeet? impl-needed
           Keywords|                            |patch

--- Comment #3 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2010-04-21 05:53:51 PDT ---
Spec meeting agenda.

HTML:
http://people.freedesktop.org/~smcv/telepathy-spec-location/spec/org.freedesktop.Telepathy.Connection.Interface.Location.html

gitweb:
http://git.collabora.co.uk/?p=user/smcv/telepathy-spec-smcv.git;a=shortlog;h=refs/heads/location

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

>From the department of reality-compliance:

Someone will need to make sure this can be implemented in Gabble before we
merge it. A suitable dummy implementation would be:

* decide the value of CanSetLocation before going CONNECTED and store it in the
GabbleConnection (but don't hook it up to D-Bus)

* confirm that "Before publishing location for the first time, if this has not
been set by a client, implementations SHOULD set it to be as restrictive as
possible" is actually implemented

* confirm that setting both the location and the location access-control type
works

* write a dummy implementation of SetLocationAndControl (bonus points if you
make SetLocation and Set(Location, AccessControl) be implemented in terms of
it!)

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