[Telepathy] Requestotron use-cases, part 6 (more dispatching)

[Simon McVittie]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 29 Apr 2008 at 17:53:34 +0100, Simon McVittie wrote:
> HTML at <http://people.collabora.co.uk/~smcv/dispatch.html>, Darcs branch
> at <http://monkey.collabora.co.uk/tp-spec-smcv-usecases> (it's written
> in reStructuredText), current text later in this email for easy quoting.

As promised in part 5, here are some more dispatch use-cases gathered
from the mailing list and further discussion.

diff -rN -u -p old-tmppMZkwt/doc/dispatch.txt new-tmppMZkwt/doc/dispatch.txt
- --- old-tmppMZkwt/doc/dispatch.txt	2008-06-05 13:41:23.962169888 +0100
+++ new-tmppMZkwt/doc/dispatch.txt	2008-06-05 13:41:23.994171888 +0100
@@ -196,15 +196,29 @@ Current implementation::
 
 Problems and variations: same as dis1_
 
- -_`dis14`: Forcibly joining a chatroom
- -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+_`dis14`, _`dis28`: Forcibly joining a chatroom
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
- -Benvolio connects to an irssi-proxy or other IRC bouncer running on some colo
- -box somewhere. The proxy informs his client that he is already in #telepathy
- -and #farsight.
+Benvolio connects to an irssi-proxy, bip or other IRC bouncer running on some
+colo box somewhere. The proxy informs his client that he is already in
+#telepathy and #farsight.
 
 Current implementation: same as dis7_, but Benvolio is already in the members
- -set for those channels
+set for those channels.
+
+Problems:
+
+* Empathy's filter (notification icon) considers these channels to be incoming
+  and waits for the first received message before blinking the status icon,
+  which means Benvolio thinks his proxy instance has lost its connection
+  to those channels
+
+Issues to bear in mind:
+
+* These Text channels are neither incoming nor outgoing - they are in
+  a third state, "automatically created". In the current version of
+  tp-spec-smcv-requests they would have state Channel_Direction_Automatic,
+  the same as contact groups and contact lists.
 
 Incoming VoIP calls
 -------------------
@@ -423,7 +437,7 @@ Problems:
 .. _Clique: http://telepathy.freedesktop.org/xmpp/clique.html
 
 _`dis22`: Invited to be a client in an existing UDP/TCP client/server protocol
- -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 (Use-cases req24, req25)
 
@@ -435,5 +449,78 @@ her a VNC connection to his computer so 
 Romeo offers Mercutio and Benvolio access to an OpenArena server running
 on his local computer.
 
+Failures and other exceptional cases
+------------------------------------
+
+_`dis23`: Client-side blocking
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Rosalind has blocked messages and calls from Romeo. However, her IM service
+does not support server-side blocking, so her client must implement blocking
+on the client side.
+
+(A similar approach can be used to implement other privacy models, such as
+"only allow messages from contacts on my publish list".)
+
+Current implementation: a filter in Mission Control 4.x
+
+Miscellaneous
+-------------
+
+_`dis24`: multiple notification mechanisms
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+(From Frederic Peters on the mailing list)
+
+Frederic wants to see IM messages appear as some sort of overlay when Totem
+is running full-screen.
+
+Problems:
+
+* Having Totem, mplayer, OpenArena and every other full-screen app know about
+  Telepathy messages, gnome-power-manager low-battery warnings and every other
+  source of notifications doesn't really scale. Can't we solve this at the
+  level of the fd.o Desktop Notification spec instead?
+
+_`dis25`: brightness on portable devices
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+(From the Nokia Internet Tablets, but also generally applicable)
+
+Naba's Internet tablet dims the screen when not in use. When a message
+or call comes in, the screen backlight should come up to normal brightness.
+
+Current implementation: a filter in Mission Control 4.x?
+
+Problems: is this really just a special case of dis24_?
+
+_`dis26`: multiple channel handers available - 1
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Romeo has both Kopette and Empathy installed on his system and both clients are
+able to handle text channels. Romeo wants to be able to choose between kopette
+and empathy just like he can choose between epiphany and firefox to handle http
+urls (see gnome-default-applications-properties).
+
+Problems:
+
+* There is no way currently to choose between channel handlers, Mission Control
+  4.x only accepts one chandler.
+
+_`dis27`: multiple channel handers available - 2
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Romeo has both Empathy and Elisa installed. When elisa is running fullscreen he
+wants it to handle outgoing and incoming calls, otherwise he wants empathy to
+handle them.
+
+Problems:
+
+* There is no way currently to choose between channel handlers, Mission Control
+  4.x only accepts one chandler.
+* Empathy's filter will get the media channel before elisa's chandler, so the
+  status icon will blink and Romeo won't see it because elisa is running
+  fullscreen.
+
 ..
   vim:set sw=4 sts=4 et:
-----BEGIN PGP SIGNATURE-----

iD8DBQFIR+t6WSc8zVUw7HYRAtXIAJ9jEQoV2rDzjZ5acuCx8aqeyaxFRQCfbFJo
0I6l+iaabTcA01XwDiwX8nk=
=F7Dj
-----END PGP SIGNATURE-----