Hi jbdhl, You can choose Slim3, too. Please see the following tutorial using GWT. http://sites.google.com/site/slim3appengine/getting-started-with-gwt
Slim3 supports HOT reloading when you use GWT, too. HOT reloading means new version of a class is automatically reloaded on the fly. Due to HOT reloading, when you change the source code, you can see the changed result on your browser without restarting web application. Yasuo Higa On Sun, Apr 25, 2010 at 4:04 AM, jbdhl <[email protected]> wrote: > Hi > > I really can't decide which datastore abstraction to use for my app. > Any help deciding, would be much appreciated! > > The app is build using GWT and there is a lot of one-to-many relations > (so I would value if all children could be automatically deleted if > the parent is deleted). > > So... Which one of JDO, Objectify or Twig-Persist should I use? > > * Twig > Pros: simple, low startup latency > Cons: only one developer (major drawback), GAE-only > > * Objectify > Pros: simple, low startup latency > Cons: slightly more verbose syntax than in Twig, GAE-only > > * JDO > Pros: not GAE-only > Cons: complex, long startup latency > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
