svn commit: r792904 - /websites/staging/esme/trunk/content/docs/apis/api.html

[bu...@apache.org]

Author: buildbot
Date: Sun Jul 17 13:40:25 2011
New Revision: 792904

Log:
Staging update by buildbot

Modified:
    websites/staging/esme/trunk/content/docs/apis/api.html

Modified: websites/staging/esme/trunk/content/docs/apis/api.html
==============================================================================
--- websites/staging/esme/trunk/content/docs/apis/api.html (original)
+++ websites/staging/esme/trunk/content/docs/apis/api.html Sun Jul 17 13:40:25 2011
@@ -55,10 +55,10 @@
     <h3 id="apis">APIs</h3>
 <table>
 <tr><th>Name </th><th> Description </th><th> Default URL prefix </th><th> Status </th></tr> 
-<tr><td>Original</td><td>Original API]</td><td> *Deprecated* \- This is our original "REST-like" API</td><td>/api</td><td>Available</td></tr>
-<tr>[Streaming](api-2.0---design.html)]</td><td>*Current* \- This is our newest API that deals allows for streaming-based access</td><td>/api2</td><td> Available</td></tr>
-<tr>[Twitter](twitter-api.html)</td><td> *Twitter* \- We also support the Twitter API which allows for clients that support laconica to also use Apache ESME/td><td> /twitter</td><td>Available</td></tr>
-<tr>[JMX|ESME](jmx-rest-api.html)</td><td>This is an API that will users to access JMX-based</td><td>/jmx</td><td>Currently being designed</td></tr>
+<tr><td>Original</td><td>Original API]. This is our original "REST-like" API</td><td>/api</td><td>Available</td></tr>
+<tr><td>[Streaming](api-2.0---design.html)]</td><td>Current \- This is our newest API that deals allows for streaming-based access</td><td>/api2</td><td> Available</td></tr>
+<tr><td>[Twitter](twitter-api.html)</td><td> The old Twitter API /td><td> /twitter</td><td>Available</td></tr>
+<tr><td>[JMX](jmx-rest-api.html)</td><td>This is an API that will users to access JMX-based</td><td>/jmx</td><td>Currently being designed</td></tr>
 </table>
 
 <p><em>Note</em>: <em>It is possible to change the used URL prefixes for the individual
@@ -67,8 +67,7 @@ APIs via properties.</em></p>
 <p><em>Clients should be developed using /api2.</em></p>
 <p>If you wish to use a API, then you must take the server name and add the
 URL prefix.</p>
-<p>For example, <em>[http://esmecloudserverapache.dickhirsch.staxapps.net/twitter]
-</em></p>
+<p>For example,http://esmecloudserverapache.dickhirsch.staxapps.net/twitter</p>
 <h5 id="token">Token</h5>
 <p>All these APIs require that you use a token.</p>
   </div>