[Dcplusplus-commit] SF.net SVN: adc:[98] trunk/ADC.txt

[<ul...@us...>]

Revision: 98
          http://adc.svn.sourceforge.net/adc/?rev=98&view=rev
Author:   ullner
Date:     2013-02-23 18:53:59 +0000 (Sat, 23 Feb 2013)
Log Message:
-----------
Specified token use from server party in client-client connections.

Modified Paths:
--------------
    trunk/ADC.txt

Modified: trunk/ADC.txt
===================================================================
--- trunk/ADC.txt	2013-02-23 17:56:49 UTC (rev 97)
+++ trunk/ADC.txt	2013-02-23 18:53:59 UTC (rev 98)
@@ -28,6 +28,7 @@
 
 * Added examples for each command.
 * Features are now described in its own section.
+* Specified token use from server party in client-client connections.
 
 === Version 1.0.2, 2013-01-31
 Fredrik Ullner <ul...@gm...>
@@ -667,9 +668,9 @@
 Connect to me. Used by active clients that want to connect to someone, or in
 response to RCM. Only TCP active clients may send this. <token> is a string
 that identifies the incoming connection triggered by this command and must be
-present in the INF command of the connecting client. Clients should not accept
-incoming connections with a token they did not send earlier. <protocol> is an
-arbitrary string specifying the protocol to connect with; in the case of an
+present in the INF command of the connecting client. Implementations should not accept
+incoming connections with a token that was not sent earlier. The server party may, but should not, provide the token in its INF. 
+<protocol> is an arbitrary string specifying the protocol to connect with; in the case of an
 ADC 1.0 compliant connection attempt, this should be the string "ADC/1.0". If
 <protocol> is supported, a response to RCM must copy the <token> and
 <protocol> fields directly. If a protocol is not supported, a DSTA must be

This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.