On 2011-05-10, at 10:22 AM, David Avendasora wrote: > > On May 9, 2011, at 8:15 PM, Pascal Robert wrote: > >> >> 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 > > Interesting, but not really on my list of things to have ERRest do... There's > regular WOComponents and D2W for HTML, no need to add another option, IMHO. > >> • ERRest + Dojo >> • ERRest + Titanium >> • ERRest + SproutCore > > This would be interesting from the perspective of what REST means to each of > those technologies and how that reconciles with ERRest's concepts. > >> • Authentification >> • Basic, Digest >> • Token >> • Sessions > > +1,000,000! I think after the basics, this is the #1 nut for any ERRest > project to crack.
Yeah, agreed, this would pre-emptively answer many list questions. > >> • JSR-311 > > This would be nice to have a solid explanation of, but I don't think it needs > a lot of time. > >> • Query args (batching, sorting) >> • Batching >> • ERXRestNameRegistry >> • Caching headers >> • Many-to-many relationships >> • ERAttachment support >> • File uploads > > These sound like a good grouping for a ERRest - Beyond the Basics session. Also agree, especially on the Query/Batching stuff, ...wait, crap, what the hell is going on here? Did I just completely agree with you? Shite, I've got to go and rethink my life-path now. > >> HATEOAS > >> JSON Referencing > > These two seem a bit abstract and academic for a good presentation. Maybe a > slide introducing the concepts and pointers to places to learn more about > them. > >> >> 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 (Webobjects-dev@lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> http://lists.apple.com/mailman/options/webobjects-dev/webobjects%40avendasora.com >> >> This email sent to webobje...@avendasora.com >> >> > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/webobjects-dev/dleber_wodev%40codeferous.com > > This email sent to dleber_wo...@codeferous.com > ;david -- David LeBer Codeferous Software 'co-def-er-ous' adj. Literally 'code-bearing' site: http://codeferous.com blog: http://davidleber.net profile: http://www.linkedin.com/in/davidleber twitter: http://twitter.com/rebeld -- WOWODC 2011 : July 1-2-3, Montreal. http://wowodc.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com