Re: Modeling button presses that invoke server side actions via REST

2010-01-14 Thread kevinpauli
"contents" of widget 123 > /myapp/widget/123/status // for the status of widget 123 > > --tim > -- View this message in context: http://n2.nabble.com/Modeling-button-presses-that-invoke-server-side-actions-via-REST-tp4375243p4392724.html Sent from the Restlet

Re: Modeling button presses that invoke server side actions via REST

2010-01-14 Thread Thierry Boileau
f different actions that could be taken on a > widget, and > therefore dozens of if-then-elses. What am I missing here? My > gut tells me > I haven't modeled my resources correctly, or I'm missing a particular > resource abstraction that would h

Re: Modeling button presses that invoke server side actions via REST

2010-01-13 Thread Rhett Sutphin
magine dozens of different actions that could be taken on a widget, and > therefore dozens of if-then-elses. What am I missing here? My gut tells me > I haven't modeled my resources correctly, or I'm missing a particular > reso

Re: Modeling button presses that invoke server side actions via REST

2010-01-13 Thread Tim Peierls
t, > and > therefore dozens of if-then-elses. What am I missing here? My gut tells > me > I haven't modeled my resources correctly, or I'm missing a particular > resource abstraction that would help. > > -- > View this message in context: > http://n2.nabble.com/Modelin

Modeling button presses that invoke server side actions via REST

2010-01-13 Thread kevinpauli
tions that could be taken on a widget, and therefore dozens of if-then-elses. What am I missing here? My gut tells me I haven't modeled my resources correctly, or I'm missing a particular resource abstraction that would help. -- View this message in context: http://n2.nabble.com/Mo