I agree. Using protocol buffers directly is not necessary (btw datastore should use them internally, as Nick Johnson explains here: http://blog.notdot.net/2010/09/Under-the-hood-with-App-Engine-APIs).
Use them only if usual datastore APIs don't satisfy your needs and you have to resort to serialized objects. In that case protocol buffers give you a maintainable data structure, otherwise using datastore APIs is certainly the best way to go. Regards Lorenzo On Oct 16, 7:39 pm, Jeff Schnitzer <[email protected]> wrote: > On Fri, Oct 15, 2010 at 11:44 PM, Guillaume B. > > <[email protected]> wrote: > > > perhaps this is an useless question and the best way to do would take me a > > lot of time for just a small performance gain > > I think this is your answer right here. Don't optimize prematurely - > build your app as quickly as possible and then find out where the real > bottlenecks are with appstats. > > Jeff -- 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.
