You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@esme.apache.org by bu...@apache.org on 2011/07/17 16:32:30 UTC
svn commit: r792920 -
/websites/staging/esme/trunk/content/docs/apis/api-2.0---design.html
Author: buildbot
Date: Sun Jul 17 14:32:30 2011
New Revision: 792920
Log:
Staging update by buildbot
Modified:
websites/staging/esme/trunk/content/docs/apis/api-2.0---design.html
Modified: websites/staging/esme/trunk/content/docs/apis/api-2.0---design.html
==============================================================================
--- websites/staging/esme/trunk/content/docs/apis/api-2.0---design.html (original)
+++ websites/staging/esme/trunk/content/docs/apis/api-2.0---design.html Sun Jul 17 14:32:30 2011
@@ -147,8 +147,7 @@ methods with an extra parameter. I think
to resource verbs, is worth using these methods in the specification and
defining the simulation method for the entire API separately.</p>
<p><a name="API2.0-Design-"></a></p>
-<h2 id="" />
-<p>Note on the call: *<a href="http://esmecloudserverapache.dickhirsch.staxapps.net/api2/user/messages?via=SAPRiver&tag=bob&message=User+'">api2/user/messages</a></p>
+<p><em>Note on the call: </em><a href="http://esmecloudserverapache.dickhirsch.staxapps.net/api2/user/messages?via=SAPRiver&tag=bob&message=User+'">api2/user/messages</a></p>
<p>That call uses "tag", not "tags". Looking at the API2 code, the parameter
name needs to be "tags". </p>
<p>When it does work, I think the behavior may be a bit misleading, as tags