Memcache is shared across your application instances. It's a separate
process.
On Fri, May 14, 2010 at 7:01 PM, Thomas wrote:
> Hi Jaroslav:
>
> GAE is currently single-homed
> according to
> http://groups.google.com/group/google-appengine-java/browse_thread/thread/cccb943347b3c6a7/338eede3100f3
Hi Jaroslav:
GAE is currently single-homed
according to
http://groups.google.com/group/google-appengine-java/browse_thread/thread/cccb943347b3c6a7/338eede3100f366
On 5月14日, 下午7時41分, Jaroslav Záruba wrote:
> ...I just want to be sure. I had the impression that two 'my' JVMs
> might not even resi
Does it mean Memcached === the Memcache we use within AppEngine?
I'm particularly interested in whether AppEngine Memcache is shared
among all the JVMs that have been started for my application. Based on
this I assume yes:
"High performance scalable web applications often use _a distributed_
in-mem
thanks for the link.
have tried the @version with shards. the output counter seems not to
be unique... i think there is no other way to mimic the sequence
generator like other rdbms without using normal transactions with
optimistic locking of the entity.
On Mar 12, 1:49 am, datanucleus wrote:
>
> could you give me simple example on how to use the @version,
The DataNucleus docs define that, and much more
http://www.datanucleus.org/products/accessplatform/jdo/orm/versioning.html
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" gro
Hi blake,
could you give me simple example on how to use the @version, or any
reference material?
thanks!
On Mar 9, 11:35 pm, Blake wrote:
> You could also go with the sharded counter strategy. The more shards
> you have, the less the chance that you'll have a collision, and you'd
> use @Versi
You could also go with the sharded counter strategy. The more shards
you have, the less the chance that you'll have a collision, and you'd
use @Version for optimistic locking on each shard.
On Mar 9, 7:18 am, legendlink wrote:
> Thanks for the reply.
>
> If memcache is used, how do I implement i
Thanks for the reply.
If memcache is used, how do I implement it so that the counter would
always be updated and not be deleted?
On Mar 6, 4:35 am, "Ikai L (Google)" wrote:
> Have you looked into Memcache's INCR?
>
> http://code.google.com/appengine/docs/java/javadoc/com/google/appengi...,
> lon