From: Georg Bauhaus <rm.dash-bauhaus@futureapps.de>
Subject: Re: Introducing memcache-ada, a memcached client in Ada
Date: Tue, 21 Dec 2010 12:10:21 +0100
Date: 2010-12-21T12:10:22+01:00 [thread overview]
Message-ID: <4d108b1e$0$6761$9b4e6d93@newsspool3.arcor-online.net> (raw)
In-Reply-To: <m2r5dcovqu.fsf@pushface.org>
On 21.12.10 00:44, Simon Wright wrote:
> For instance, you could implement Expiring_After > 30 days by
> calculating the absolute time & passing that instead .. in fact, why not
> do that always? (that's how GNAT implements 'delay').
Passing the absolute times with cached objects? For illustration,
the way Google's cloud seems to handle points in time renders this
adventurous, I think. A Google App Engine program will typically
use memcached. Depending on the node executing the parts
of your software, "absolute" times may be shifted by
several hours in some direction. I haven't found a rule yet
by which I could predict times. E.g., it is 12-17 06:04AM 54.659
Google time now, my wall clock showing 12:04AM for this.
I understand Google App Engine programs can have parts moved
between nodes.
In a setting as volatile as this, a "time span" associated with
a cached object seems preferable.
next prev parent reply other threads:[~2010-12-21 11:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 0:43 Introducing memcache-ada, a memcached client in Ada R Tyler Croy
2010-12-20 8:25 ` Thomas Løcke
2010-12-20 10:16 ` Georg Bauhaus
2010-12-20 9:36 ` Thomas Løcke
2010-12-20 20:14 ` R Tyler Croy
2010-12-21 0:56 ` Randy Brukardt
2010-12-21 7:52 ` Dmitry A. Kazakov
2010-12-20 19:36 ` Jeffrey Carter
2010-12-20 20:16 ` R Tyler Croy
2010-12-20 22:03 ` Simon Wright
2010-12-20 22:48 ` R Tyler Croy
2010-12-20 23:44 ` Simon Wright
2010-12-21 11:10 ` Georg Bauhaus [this message]
2010-12-21 11:21 ` Georg Bauhaus
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox