svn commit: r1140976 - /esme/site/trunk/content/docs/apis/api-2.0---design.mdtext

[rh...@apache.org]

Author: rhirsch
Date: Wed Jun 29 06:50:37 2011
New Revision: 1140976

URL: http://svn.apache.org/viewvc?rev=1140976&view=rev
Log:
working on files

Modified:
    esme/site/trunk/content/docs/apis/api-2.0---design.mdtext

Modified: esme/site/trunk/content/docs/apis/api-2.0---design.mdtext
URL: http://svn.apache.org/viewvc/esme/site/trunk/content/docs/apis/api-2.0---design.mdtext?rev=1140976&r1=1140975&r2=1140976&view=diff
==============================================================================
--- esme/site/trunk/content/docs/apis/api-2.0---design.mdtext (original)
+++ esme/site/trunk/content/docs/apis/api-2.0---design.mdtext Wed Jun 29 06:50:37 2011
@@ -1,35 +1,4 @@
 Title: API 2.0 - Design
-{float:right|width=40%}
-{panel:title=Contents}
-   * [Streams vs. Resources](#API2.0-Design-Streamsvs.Resources)
-   * [Resource/Object/Stream Hierarchy](#API2.0-Design-Resource/Object/StreamHierarchy)
-   * [Methods, Resources, and Descriptions](#API2.0-Design-Methods,Resources,andDescriptions)
-   * [](#API2.0-Design-)
-   * [Streams](#API2.0-Design-Streams)
-      * [Authorization and roles](#API2.0-Design-Authorizationandroles)
-      * [ESME HTTP Comet/long-polling implementation for streams](#API2.0-Design-ESMEHTTPComet/long-pollingimplementationforstreams)
-      * [Streams/Message-queues in ESME and in general](#API2.0-Design-Streams/Message-queuesinESMEandingeneral)
-   * [Formats](#API2.0-Design-Formats)
-      * [Request formats](#API2.0-Design-Requestformats)
-      * [Response formats](#API2.0-Design-Responseformats)
-   * [Authorization](#API2.0-Design-Authorization)
-   * [Clients](#API2.0-Design-Clients)
-{panel}
-
-{panel:title=Points for discussion, resolution, further work}
-1. Is the use of HTTP sessions necessary? Is it desirable?
-1. Request signing methods?
-1. Payload and response schemas must be defined
-1. Should API contain admin functions?
-1. Webhooks ([http://blog.webhooks.org/](http://blog.webhooks.org/)
-)
-1. * ESME has webhooks as part of its actions framework, but we may want to document their existence as part of the API, and possibly improve the functionality if there are use cases ([http://incubator.apache.org/esme/actions.html](http://incubator.apache.org/esme/actions.html)
-)
-1. What is a conversation?
-1. Authorization approach (see above)
-1. What is our streaming approach?
-{panel}
-{float}
 
 <a name="API2.0-Design-Streamsvs.Resources"></a>
 ## Streams vs. Resources
@@ -132,7 +101,7 @@ defining the simulation method for the e
 <a name="API2.0-Design-"></a>
 ## 
 
-{panel}
+
 *Note on the call:&nbsp;*[api2/user/messages](http://esmecloudserverapache.dickhirsch.staxapps.net/api2/user/messages?via=SAPRiver&tag=bob&message=User+')
 
 That call uses "tag", not "tags". Looking at the API2 code, the parameter
@@ -142,7 +111,6 @@ When it does work, I think the behavior 
 added using the tags parameter do not necessarily show up in the message at
 all. So make sure to keep an eye on the tag cloud or go to the page for the
 specific tag you are trying to add and see if it shows up there.
-{panel}
 
 <a name="API2.0-Design-Streams"></a>
 ## Streams