[asterisk-commits] russell: branch russell/messaging r297577 - /team/russell/messaging/doc/

[SVN commits to the Asterisk project]

Author: russell
Date: Fri Dec  3 16:56:48 2010
New Revision: 297577

URL: http://svnview.digium.com/svn/asterisk?view=rev&rev=297577
Log:
remove a testing todo

Modified:
    team/russell/messaging/doc/asterisk-messaging.txt

Modified: team/russell/messaging/doc/asterisk-messaging.txt
URL: http://svnview.digium.com/svn/asterisk/team/russell/messaging/doc/asterisk-messaging.txt?view=diff&rev=297577&r1=297576&r2=297577
==============================================================================
--- team/russell/messaging/doc/asterisk-messaging.txt (original)
+++ team/russell/messaging/doc/asterisk-messaging.txt Fri Dec  3 16:56:48 2010
@@ -207,26 +207,8 @@
 up into the Asterisk core for processing as an Asterisk message.  An option will
 be provided to disable authentication for out of dialog MESSAGE, in case someone
 would like to use it as a message transport between applications doing end to
-end security in the MESSAGE body.
-
-    At some point, we would like to provide support for SIP SIMPLE (INVITE
-dialogs with an MSRP stream).  One of the nice aspects of that for Asterisk
-would be to be able to authenticate a client wishing to send messages to
-Asterisk, but without having to authenticate every MESSAGE request.  Until full
-MSRP support can be developed, a less ideal alternative for an authenticated
-message dialog is being proposed.  If a client sends a SUBSCRIBE to Asterisk for
-the "x-messages" event package, then messages directed to that SIP peer will be
-delivered as a NOTIFY in that dialog.  Further, if configured to do so, Asterisk
-will SUBSCRIBE to "x-messages" from the same peer when it subscribes.  A NOTIFY
-received in that dialog will be passed up into Asterisk to be processed as a
-message.
-
-    Admittedly, this usage of SUBSCRIBE isn't pretty.  However, it solves a
-short term problem.  Unauthenticated MESSAGEs is not ideal from a security point
-of view.  Authenticating every MESSAGE is not ideal due to the increased load it
-imposes on the Asterisk server.  So, this mechanism allows for an authenticated
-way to get messages in and out of Asterisk's text messaging architecture over
-SIP without excess load on the server.
+end security in the MESSAGE body.  We will also have support for sending an
+out-of-call MESSAGE by using the MessageSend() application.
 
 --------------------------------------------------------------------------------
 --------------------------------------------------------------------------------
@@ -273,9 +255,6 @@
        adding headers for messages that is not the same one used to add headers
        for outbound calls?
 
-    -> Add automated tests for:
-       - disabling out of call MESSAGE completely
-
 XMPP (res_jabber):
 
     -> Make the message queue internal to res_jabber for JABBER_RECEIVE()