Le 2011-05-09 à 18:37, Daniel Beatty a écrit :

> Greetings Pascal,
> Both a general and specific set of topics would be nice.   Like for example, 
> last year's talk you gave proved very useful.    Strengths and limitations of 
> REST may be a useful topic.   What standards do exist for REST, and how WO 
> can help on this front (given the hordes of IBM and others who will shoot it 
> down if they don't understand it).   
> 
> Anywho, this is just a thought.

For the fun of it, this is the list of potentials topics:

        • HTML routing
                • Automatic vs manual 
                • Linking between pages 
(ERXRouteUrlUtils/ERXRouteLink/ERXRouteURL)
                • Offline access/cache
        • ERRest + Dojo
        • ERRest + Titanium
        • ERRest + SproutCore
        • Authentification
                • Basic, Digest
                • Token
                • Sessions
        • JSR-311
        • Query args (batching, sorting)
        • Batching
        • ERXRestNameRegistry
        • Caching headers
        • Many-to-many relationships
        • ERAttachment support
        • File uploads
        HATEOAS
        JSON Referencing

HTML routing and ERRest + Dojo are a go. It's the other topics that I don't 
know which ones to do (HATEOAS and caching headers are two favorites).

> Dan
> 
> 
> 
> 
> 
> On May 9, 2011, at 12:12 PM, Pascal Robert wrote:
> 
>> list of topics for my ERRest presentation at WOWODC, but since according to 
>> the survey a lot of you are already using ERRest and a good chunk will start 
>> using it, I was wondering if you wanted to see some specific topics. I will 
>> not talk about iOS development because I don't do such (I think David LB 
>> will talk a bit about it), but any other stuff 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:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to