I should have been clearer. The AppEngine documents themselves are above par, it took only a few hours to proof of concept what I wanted from them. Should people switch to GWT, AppEngine, GData.. Is it going to save time, money, be more reliable. I like finding out my making something small.
>From what I've seen so far, which isn't enough time to form a quality opinion - the GAE,GWT, and GDATA teams think it is a race, and they're leaving pitfalls for each other's users scattered throughout. At about hour 12-20 of prototyping you hit a cyclone in the middle. This thing spun me so completely I thought I was going a need a team from M.I.T. to come in to oAuth2. Something that is done & done, I wrote a oAuth2/data library for my classic TI83+ that prototypes better. There is a large mixture of version 2.x.x, 1.0.x, 1.0.x, 550.x.x.x (client or server side). When combining gdata,gwt,gae. There are code branches linked with aged, dead solutions to the simplest problems, 25 different OAuth2 pages stating/implementing the same thing completely differently. I know the concepts, it'd be awesome to have a functioning/reusable syntax. I must have missed the super important golden link that has quality information (flow charts,spreadsheets,functional repository code samples). I find a small drawing worth more than a 40,000 word dialog of a person mentally masturbating to his architecture. Ketamine trips have less holes to fall in. On Sep 21, 12:59 am, Tim Hoffman <zutes...@gmail.com> wrote: > I would strongly agree with Robert, and not agree with the OP. > I find the appengine docs are fine, everything can do with improvement > though ;-) > > Just my 2c worth > > T -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
