The reason is speed. Given I'm have game, for example. When ever a player make a move, I need to update the game details. Only when the game finish that I want to persist them to datastore (for later reference).
On Apr 23, 10:06 pm, Romain Pelisse <[email protected]> wrote: > +1 > > Why are you looking to that on memcache rather than with the datastore ? > > It could definitelly be sounded approach, I would just like to know the > reasons behind ... > > Le 23 avr. 2010 15:00, "James" <[email protected]> a écrit : > > It sounds like you're looking for memcached CAS > -http://groups.google.com/group/memcached/browse_thread/thread/b98fc70... > > Of course, this all begs the question of what you do if your data is > expunged from memcached. Are you not also writing to the datastore > (which has its own concurrency mgmt for cases like these)? > > James > > On Apr 23, 12:23 am, Phuong Nguyen <[email protected]> wrote:> Hi guys: > > I'm creating an app t... > > 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 fo... > > -- > 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.
