[Telepathy-commits] [telepathy-spec/master] Propose implementation for dis11 and explain why it's a good idea

[Simon McVittie]

20080625161146-53eee-ab117037100224c76d50d776c8e11eff0968827c.gz
---
 doc/dispatch.txt |   17 +++++++++++++----
 1 files changed, 13 insertions(+), 4 deletions(-)

diff --git a/doc/dispatch.txt b/doc/dispatch.txt
index 232333a..7e7a647 100644
--- a/doc/dispatch.txt
+++ b/doc/dispatch.txt
@@ -430,12 +430,21 @@ Problems:
   a handler for contact lists - this excludes the possibility of a third-party
   process that does the same thing
 
-Best-practice solution:
+* Client authors would prefer to wait for all contact lists to arrive (or
+  definitely not arrive), then query for all those contacts' aliases, avatars
+  etc. in one big transaction, and only then display them - but that's
+  impossible if the client is being passive, because it can't know whether
+  the 'publish' channel hasn't arrived yet, or will never arrive because the
+  CM doesn't support it
 
-* Clients SHOULD NOT be channel handlers for contact lists; clients SHOULD
-  explicitly request any contact list channels that they want to use
+Proposed implementation:
+
+* Clients SHOULD NOT rely on being channel handlers for contact lists;
+  clients SHOULD explicitly request any contact list channels that they want
+  to use
 
-* Perhaps clients interested in contact lists should be observers instead?
+* Clients interested in contact lists should be Observers and observe them,
+  instead of relying on being a channel handler
 
 _`dis12`: A user-defined contact group is found during login
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- 
1.5.6.5