http://www.wocommunity.org/podcasts/wowodc/2011/ERRest.mov

http://www.slideshare.net/wocommunity/er-rest-thenextsteps

> Hi!
> 
> Is there any chance I could get this presentation? I am playing with ERRest, 
> and must implement some form of authentication. Your first step tutorial was 
> perfect but it would be great to see the next part!
> 
> My goal is for another app to access this ERRest app with some kind of 
> api-key.
> 
> /Fredrik Lindgren
> 
> 6 apr 2012 kl. 15:35 skrev Pascal Robert <[email protected]>:
> 
>> Ok, so I'm going to copy Chuck and Kieran :-) What do you wish to learn in 
>> the ERRest sessions?
>> 
>> For the ERRest Boot Camp, I'm thinking of showing how to build the 
>> SimpleBlog example step by step. That will include how to add the routes, 
>> create key filters, supporting more than one format and how to create HTML 
>> REST components.
>> 
>> For ERRest in Depth, it would be a bit like the Ajax session from Chuck in 
>> 2011. We will go over how the internals of ERRest works, and how to add new 
>> features (authentication and a new format, maybe Atom).
>> 
>> From experience, it seems the number one problem that WO developers have 
>> with REST is that it's stateless and people have problems understanding how 
>> routes and URLs are related, so I will put extra efforts on explaining 
>> those. 
>> 
>> Anything else you want to learn about?
>> 
>> 
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list      ([email protected])
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/webobjects-dev/frelin%40timeoff.se
>> 
>> This email sent to [email protected]
>> 
> 


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to