From c5e09cf82446ab4c7bb82626acc5cf1eafef0014 Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Mon, 30 Jan 2012 15:55:33 +0000 Subject: [PATCH] Add rationale for SupportedLocationFeatures, Can_Set Taken from my earlier branch which added a separate CanSet boolean property. --- spec/Connection_Interface_Location.xml | 33 ++++++++++++++++++++++++------- 1 files changed, 25 insertions(+), 8 deletions(-) diff --git a/spec/Connection_Interface_Location.xml b/spec/Connection_Interface_Location.xml index c4fd68c..49593fb 100644 --- a/spec/Connection_Interface_Location.xml +++ b/spec/Connection_Interface_Location.xml @@ -416,19 +416,36 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. - Indicates the Location features supported by this connection. This - property MAY be undefined before Status - becomes Connected, but MUST remain constant thereafter. +

Indicates the Location features supported by this connection. This + property MAY be undefined before Status + becomes Connected, but MUST remain constant thereafter.

+ + +

On XMPP, you don't know what the server supports until you ask it. + The definition of this property implies that implementations using + XMPP will need to check whether the server supports PEP before moving + to the CONNECTED state.

+
- - Indicates that setting your own location with - SetLocation is supported on this - connection. + +

Indicates that setting your own location with + SetLocation + is supported on this connection.

+ + +

On XMPP, Location is advertised in a PEP node. If the user is + connected to a server that doesn't support PEP (like Google Talk), + they can't advertise their own location; however, the Location + interface should still appear in Connection.Interfaces, since the user can still + retrieve other contacts' locations.

+
-- 1.7.9.1