I just modified DAOBase to make it easier to pass in an ObjectifyOpts. You can either grab that from subversion or make your own copy; DAOBase is only a handful of lines of code and really just serves as an example of one useful way of using Objectify.
http://code.google.com/p/objectify-appengine/source/browse/trunk/src/com/googlecode/objectify/helper/DAOBase.java Jeff On Fri, May 14, 2010 at 3:00 AM, Toby <[email protected]> wrote: > Hello Jeff, > > Thank you for your advice. I actually do not need transactions so it > is perfect for me that this is the default. > I do not need strong consistency. This might speed up things a bit? I > use DAOBase, how would I need configure this? > > Thanks, > Toby > p.s. the consistency thing might be worth to add to the Best Practices > page, which is excelent by the way! > > > > On May 10, 11:07 pm, Jeff Schnitzer <[email protected]> wrote: >> Objectifydoes not use the jdoconfig.xml, nor does >> NontransactionalWrite or NontransactionalRead make any sense in the >> context ofObjectifybecause the transaction API is much simpler. >> >> You can create anObjectifyinstance with various transaction or >> consistency characteristics by calling >> ObjectifyFactory.begin(ObjectifyOpts). The javadocs for ObjectifyOpts >> are here: >> >> http://objectify-appengine.googlecode.com/svn/trunk/javadoc/com/googl... >> >> (note that begin() and beginTransaction() are just convenient >> shorthands for the method that takes the options) >> >> Jeff >> >> >> >> >> >> On Mon, May 10, 2010 at 4:38 AM, Toby <[email protected]> wrote: >> > Hello, >> >> > I finally rewrote my entire app to swich from JDO toObjectify. As I >> > used DAO it was actually rather quick. I am quite astonished how easy >> >objectifyworks. Also it gives you from the very beginning on the >> > right hints to write optimal code. In JDO it took me much longer. I >> > believe a framework like that should be a standard option. >> >> > Anyhow, I got a quick question. In JDO there was the recomendation to >> > set NontransactionalWrite and NontransactionalRead to true and >> > datanucleus.appengine.datastoreReadConsistency to EVENTUAL in order to >> > speed up your applicatin (if it does not need these features). >> >> > Is there a similar thing forobjectify? Or does the jdoconfig.xml >> > apply forobjectifyas well? >> >> > Thanks, >> > Toby >> >> > -- >> > 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 >> > athttp://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 >> athttp://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. > > -- 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.
