Re: Examples of Async Restful services

On 08.05.2013, at 17:01, Erik Wilde <[email protected]> wrote:

> On 2013-05-08 07:45 , Mike Kelly wrote:
> > On 08.05.2013, at 13:26, Shaunak Kashyap <[email protected]
> > <mailto:ycombinator%40gmail.com>> wrote:
> > > I'm not sure if the callback approach is necessarily in conflict
> > with the RESTfulness of the API
> > Violates stateless server constraint.
> > Afaik, "stateless server" is not a constraint..
> 
> no it isn't.

Well, it *is* a constraint of REST - see section 5.1.3.

However, I agree that you can add pubsub to REST (i.e. WATCH in Waka). So I was wrong there.

Jan


> a PubSub mechanism such as PuSH can be layered on top of a 
> pull-oriented REST architecture with atom without violating any REST 
> constraints. PuSH simply failed to properly address subscription 
> management, but otherwise had no architectural issues. managing 
> subscriptions on the server is fine REST-wise, it's just fairly 
> expensive and thus not a style you would want to follow unless that cost 
> is justified. on a side note, since the actual messages are nicely 
> self-describes messages, PuSH allowed fairly nice optimization for the 
> push side of things, by using layered hub setups.
> 
> cheers,
> 
> dret.
> 
> -- 
> erik wilde | mailto:[email protected] - tel:+1-510-2061079 |
> | UC Berkeley - School of Information (ISchool) |
> | http://dret.net/netdret http://twitter.com/dret |
> 



------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/rest-discuss/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/rest-discuss/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/