[google-appengine] Re: How memcache work?
On Feb 1, 2:35 pm, masterzim wrote: > What happens if I access to memcache from different > request, is transactions atomic? Star this: http://code.google.com/p/googleappengine/issues/detail?id=2139&#c1 Poke Brad: http://twitter.com/bradfitz -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Re: How memcache work?
On Feb 1, 8:20 pm, Patrick Twohig wrote: > I believe that the memcache service is implemented on top of this. I could > be wrong, though:http://memcached.org/ I think I read that the creator memcached created "memcacheg" for Google. Not sure what the difference is though! To the OP - What is it you're trying to do? While you can't do transactions, there may be another way to achieve what you're trying to do using memcache. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: How memcache work?
I believe that the memcache service is implemented on top of this. I could be wrong, though: http://memcached.org/ On Mon, Feb 1, 2010 at 10:31 AM, Satoshi wrote: > There is no transaction mechanism around memcache. Although it is > technically possible to use an entity group (or groups) on the > datastore to create a transaction mechainsm on top of memcache, it > does not make sense to use slower mechanism (datastore) on top of > faster mechanism (memcache). > > Generally speaking, you should use memcache to return a "snapshot" of > data to the client. If you need transactions, go directly to the > datastore. > > Satoshi > > On Feb 1, 6:35 am, masterzim wrote: > > In official documentation I didn't find nothing about memcache > > transaction. What happens if I access to memcache from different > > request( this is save? ) , is transactions atomic? This will be great > > if somebody can explain this. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appeng...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- Patrick H. Twohig. Namazu Studios P.O. Box 34161 San Diego, CA 92163-4161 Office: 619.862.2890 x100 Cell: 619.453.5075 Twitter: @svm_invictvs IRC: svm_invic...@irc.freenode.net ##java, #android-dev, #iphonedev, #appengine http://www.namazustudios.com/ This communication, and any attachments, shall be considered confidential and proprietary information of Namazu Studios LLC. This message, and attachments, are intended for the listed recipients only. If you are not one of the intended recipients, please destroy all copies of this communication. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Re: How memcache work?
There is no transaction mechanism around memcache. Although it is technically possible to use an entity group (or groups) on the datastore to create a transaction mechainsm on top of memcache, it does not make sense to use slower mechanism (datastore) on top of faster mechanism (memcache). Generally speaking, you should use memcache to return a "snapshot" of data to the client. If you need transactions, go directly to the datastore. Satoshi On Feb 1, 6:35 am, masterzim wrote: > In official documentation I didn't find nothing about memcache > transaction. What happens if I access to memcache from different > request( this is save? ) , is transactions atomic? This will be great > if somebody can explain this. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
