document changes in 0.8.3

www.i2p2/pages/i2cp_spec.html

@@ -1,7 +1,7 @@
 {% extends "_layout.html" %}
 {% block title %}I2CP Specification{% endblock %}
 {% block content %}
-Updated February 2011, current as of router version 0.8.4
+Updated May 2011, current as of router version 0.8.5
 <h1>I2P Control Protocol (I2CP) Specification</h1>
 <h2>Overview</h2>
 <p>
@@ -474,10 +474,9 @@ The router responds with a <a href="#msg_DestReply">Dest Reply Message</a>.
 
 <h4>Notes</h4>
 <p>
-Only one Dest Lookup may be outstanding at a time.
-Currently supported only by client sessions set up with I2PSimpleSession.
-These limitations should be fixed.
 As of release 0.7.
+As of release 0.8.3, multiple outstanding lookups are supported,
+and lookups are supported in both I2PSimpleSession and in standard sessions.
 </p>
 
 
@@ -489,16 +488,19 @@ Sent from Router to Client in response to a Dest Lookup Message.
 </p>
 <h4>Contents</h4>
 <ol><li>
-<a href="common_structures_spec#struct_Destination">Destination</a> (optional)
+<a href="common_structures_spec#struct_Destination">Destination</a>
+on success, or
+<a href="common_structures_spec#struct_Hash">Hash</a>
+on failure
 </li></ol>
 
 <h4>Notes</h4>
 <p>
-If the Destination is not present, the lookup failed.
 As of release 0.7.
-In the future,
-we should return the Hash instead of nothing if the lookup failed,
-so we can have multiple lookups outstanding and correlate the replies.
+As of release 0.8.3,
+the requested Hash is returned if the lookup failed,
+so that the client may have multiple lookups outstanding and correlate the replies to the lookups.
+Prior to release 0.8.3, the response was empty on failure.
 </p>
 
 
@@ -554,9 +556,9 @@ The router responds with a <a href="#msg_BandwidthLimits">Bandwidth Limits Messa
 
 <h4>Notes</h4>
 <p>
-Currently supported only by client sessions set up with I2PSimpleSession.
-These limitations should be fixed.
 As of release 0.7.2.
+As of release 0.8.3,
+supported in both I2PSimpleSession and in standard sessions.
 </p>