sync: xmpp pubsub, multi-user chat

[skm-ma-ws1314.git] / sec-chatty-things.tex

diff --git a/sec-chatty-things.tex b/sec-chatty-things.tex
index d748494..fe69f94 100644 (file)
--- a/sec-chatty-things.tex
+++ b/sec-chatty-things.tex
@@ -4,7 +4,6 @@ After the underlying techniques have been explained, we can have a look at the
 system architecture which Klauck and
 Kirsche~\cite{Klauck:2012:BCC:2352852.2352881} use to build Chatty Things.
 
 system architecture which Klauck and
 Kirsche~\cite{Klauck:2012:BCC:2352852.2352881} use to build Chatty Things.
 

-\todo

 \pages{3}
 \subsection{Service Provisioning Sublayer}
 
 \pages{3}
 \subsection{Service Provisioning Sublayer}
 


@@ -68,8 +67,7 @@ devices of a topic, or she can also interact with them directly.
 In scenarios without an XMPP server, the XEP-0174 module is activated and
 devices talk directly with the user or with other devices. This method has the
 drawback that Multi-User Chats cannot be used for topic filtering, since no
 In scenarios without an XMPP server, the XEP-0174 module is activated and
 devices talk directly with the user or with other devices. This method has the
 drawback that Multi-User Chats cannot be used for topic filtering, since no

-method is specified to do XEP-0045 and XEP-0174 at the same time. \todo[temporary subscription presence here?]
-In this case,
+method is specified to do XEP-0045 and XEP-0174 at the same time. In this case,

 a user must have an XEP-0174-compliant chat client, but it also gives her the
 opportunity to interact with things spontaneously on an ad-hoc basis (e.~g. when
 entering a room) without need for any additional gateway on the application
 a user must have an XEP-0174-compliant chat client, but it also gives her the
 opportunity to interact with things spontaneously on an ad-hoc basis (e.~g. when
 entering a room) without need for any additional gateway on the application