You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@esme.apache.org by "Hirsch, Richard" <ri...@siemens.com> on 2009/01/21 07:27:56 UTC

REST API Thoughts

What about if we based our fundamental REST API on that of Twitter.  We wouldn't have a ESME REST API with all functionality and then the Twitter API rather we would have a Twitter API and then a smaller REST API that would contain functionality not covered by Twitter.
 
Thoughts?
 
D,

AW: REST API Thoughts

Posted by "Hirsch, Richard" <ri...@siemens.com>.

We might have to discuss would might happen if we added functionality to a REST API function from Twitter. My suggestion would be: no problem as long as the twitter functionality isn't broken. 

D. 

-----Ursprüngliche Nachricht-----
Von: Hirsch, Richard 
Gesendet: Mittwoch, 21. Jänner 2009 07:28
An: esme-dev@incubator.apache.org
Betreff: REST API Thoughts

What about if we based our fundamental REST API on that of Twitter.  We wouldn't have a ESME REST API with all functionality and then the Twitter API rather we would have a Twitter API and then a smaller REST API that would contain functionality not covered by Twitter.
 
Thoughts?
 
D,

Re: REST API Thoughts

Posted by David Pollak <fe...@gmail.com>.

On Tue, Jan 20, 2009 at 10:27 PM, Hirsch, Richard <
richard.hirsch@siemens.com> wrote:

> What about if we based our fundamental REST API on that of Twitter.  We
> wouldn't have a ESME REST API with all functionality and then the Twitter
> API rather we would have a Twitter API and then a smaller REST API that
> would contain functionality not covered by Twitter.
>
> Thoughts?


ESME messages have "more stuff" in them than do Twitter messages.

I'd rather have the ESME API and the Twitter API as separate things with
separate URLs.


>
>
> D,
>



-- 
Lift, the simply functional web framework http://liftweb.net
Collaborative Task Management http://much4.us
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp