summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJonny Lamb <jonny.lamb@collabora.co.uk>2011-05-09 16:28:12 +0100
committerJonny Lamb <jonny.lamb@collabora.co.uk>2011-05-09 16:28:12 +0100
commit5f474fac891e4518d46dd6cfd03acef9de49a33e (patch)
treeb881ee89e2c2a0d5f45f9b3bf25250fe99ed64ac
parent2a0fea193e59836b55216bf0437dce4998ea6b3e (diff)
Subject: note how CanSet might not be correcta-bit-more-room
Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
-rw-r--r--spec/Channel_Interface_Subject.xml13
1 files changed, 12 insertions, 1 deletions
diff --git a/spec/Channel_Interface_Subject.xml b/spec/Channel_Interface_Subject.xml
index 36d43c04..d60e25b5 100644
--- a/spec/Channel_Interface_Subject.xml
+++ b/spec/Channel_Interface_Subject.xml
@@ -109,7 +109,18 @@
<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
<p>TRUE if the <tp:member-ref>Subject</tp:member-ref> property
can be set by the user by calling
- <tp:member-ref>SetSubject</tp:member-ref>, otherwise FALSE.</p>
+ <tp:member-ref>SetSubject</tp:member-ref>, otherwise
+ FALSE.</p>
+
+ <p>If implementations are unsure of what this value should be
+ it SHOULD still be set to what it believes the value
+ is. As a result, clients should be aware that
+ <tp:member-ref>SetSubject</tp:member-ref> can still fail
+ even with this property set to TRUE.</p>
+
+ <tp:rationale>In XMPP it is impossible to know whether an
+ occupant can set the subject as XMPP server implementations
+ are wildly inconsistent.</tp:rationale>
<p>Change notification for this property is provided by the
standard D-Bus <code>PropertiesChanged</code> signal.</p>