From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,bdcca6db8294fb00
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news3.google.com!feeder3.cambriumusenet.nl!feeder1.cambriumusenet.nl!feed.tweaknews.nl!216.196.110.149.MISMATCH!border2.nntp.ams.giganews.com!nntp.giganews.com!news.teledata-fn.de!newsfeed.arcor.de!newsspool2.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Date: Tue, 21 Dec 2010 12:10:21 +0100
From: Georg Bauhaus <rm.dash-bauhaus@futureapps.de>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US;
 rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: Introducing memcache-ada, a memcached client in Ada
References: <slrnigt9l7.jge.tyler@kiwi.local>
	<4d0f1316$0$23759$14726298@news.sunsite.dk>
	<ieobjd$inb$1@tornado.tornevall.net>
 <m239psqezi.fsf@pushface.org>	<slrnigvn9e.5bf.tyler@kiwi.local>
 <m2r5dcovqu.fsf@pushface.org>
In-Reply-To: <m2r5dcovqu.fsf@pushface.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-ID: <4d108b1e$0$6761$9b4e6d93@newsspool3.arcor-online.net>
Organization: Arcor
NNTP-Posting-Date: 21 Dec 2010 12:10:22 CET
NNTP-Posting-Host: 0771c425.newsspool3.arcor-online.net
X-Trace: 
 DXC=Sj`BO`4UI3Q<<0iRN7DLEQMcF=Q^Z^V3X4Fo<]lROoRQ8kF<OcfhCO[`F0@kn0Cb[Rnc\616M64>ZLh>_cHTX3j]lS`Ah@2NZ\T
X-Complaints-To: usenet-abuse@arcor.de
Xref: g2news1.google.com comp.lang.ada:16095
Date: 2010-12-21T12:10:22+01:00
List-Id: <comp.lang.ada>

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.