Skip to main content

Home/ Google AppEngine/ Group items tagged jdo

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
2More

Google App Engine Cold Start Guide for Java - 0 views

www.answercow.com/...gine-cold-start-guide-for.html gaej appengine gae jsp performance tip
shared by Esfand S on 28 Sep 10 - No Cached
  • Originally my application started out using Spring MVC and JDO. The first use of JDO took my application about 5 seconds to get everything set up.  Similarily, Spring MVC added around 6 seconds to the cold start  time
  •  If you are not using either JDO or JPA, you can safely delete all related libraries (ones that have JDO, JPA, or Datanucleus in their name) and use the command line tool to upload your app. Deleting these libraries shaves about 400ms off of cold start time.
1More

Google App Engine + JAVA + JDO = Simple Search | Wet Feet - Online Marketing and Techno... - 0 views

www.wetfeetblog.com/...287 appengine sample tutorial
shared by Esfand S on 28 Sep 10 - Cached
  • Esfand S on 28 Sep 10
     
    This article will show you how to implement a simple search in Google App Engine using JDO engine including searching in child objects.
1More

JDO/JPA Snippets That Work - Serialized Fields - Google App Engine for Java | Google Gr... - 0 views

groups.google.com/...aa952f14b1c1fa96 appengine tip
shared by Esfand S on 28 Sep 10 - Cached
  • Esfand S on 28 Sep 10
     
    Serialized fields are a good way to store structured data inside the record of a containing Entity. As long as you can get by without filtering or sorting on this data and you remember that it has special update requirements, serialized fields will almost certainly come in handy at some point.
3More

Parallel Asynchronous Datastore Commands with Twig 1.0 - Google App Engine for Java | G... - 1 views

groups.google.com/...a26aebbe4d4cd0b2 gae datastore library twig lowlevel appengine
shared by Esfand S on 28 Sep 10 - Cached
  •  Twig is an alternative to the standard   persistence interfaces JDO and JPA, specifically designed to make the   most of the underlying datastore's unique features.
  • Twig is the only interface to support direct unowned relationships so   your code is not dependent on low-level datastore classes.  It is the   only interface to support OR queries by merging together multiple   queries, sorting them and filtering out duplicates at the lowest level   for performance.
  • Async datastore calls are not yet part of the low-level API.  Twig   uses the underlying Protocol Buffer layer classes to call   ApiProxy.makeAsyncCall() instead of makeSyncCall.  All the code is   open source so you can check out how its done.
1 - 9 of 9
Showing 20▼ items per page