Not to be picky, but wouldn't that scenario be just for GET REST?
(i.e. reading data)? Wouldn't you need to be able to specify actions
for GET, PUT, etc etc to be proper rest? Just spitballing here, but
that was always my understanding. The REST pattern is a complex one -
you only need look at the JAX-RS spec to see that!
It would be really interesting to see the slides from liftoff
however :)
Cheers
Tim
http://liftweb.googlecode.com/svn/trunk/liftweb/docs/presentations/lift-web-services/
I was hoping it'd be viewable directly out of SVN but it sends out the
wrong MIME type for html.
Please let me know if you have any questions.
Steve
PS You may have to resize your browser window when viewing the
presentation for all the text to appear. S5 is touchy that way.
/davidB
I didn't realize that SimpleController had vanished from lift! So,
gang, what's the preferred way to handle Web Services now?
On Thu, May 22, 2008 at 3:30 AM, Ilya Klyuchnikov
> As far as I understand SimpleController is a trait supposed to be
> defined in this example:
>
> trait SimpleController SimpleController {
> def index: ResponseIt
> def get(id: String): ResponseIt
> def create: ResponseIt
> def delete(id: String): ResponseIt
> }
>
> The rationale behind this trait is that you are able to defined many
> controllers and setup dispatching in unified way in Boot class.
>
>
> On May 22, 7:09 am, Robert Spychala <robspych...@gmail.com> wrote:
>> this is great! one question: I'm having trouble compiling the example
>> cause i can't find SimpleController. i'm using lift. 0.8? What is this
>> class and where can I find it?
>>
>> thanks!
>
> >
>