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: 
 g2news2.google.com!news3.google.com!feeder.news-service.com!85.214.198.2.MISMATCH!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: Introducing memcache-ada, a memcached client in Ada
Date: Mon, 20 Dec 2010 22:03:13 +0000
Organization: A noiseless patient Spider
Message-ID: <m239psqezi.fsf@pushface.org>
References: <slrnigt9l7.jge.tyler@kiwi.local>
	<4d0f1316$0$23759$14726298@news.sunsite.dk>
	<ieobjd$inb$1@tornado.tornevall.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: mx01.eternal-september.org;
 posting-host="dFCm8HWntFqmDIilBLqEJQ";
	logging-data="26397"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX1/FlkBy9JmZJBZaezFNspi4Nu0zkX7X/MM="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (darwin)
Cancel-Lock: sha1:9SuoJL5h2eGjeolc7MqDgH/7OZQ=
	sha1:ktshFAZVy1A3NFgmqs7Q+OqVYtM=
Xref: g2news2.google.com comp.lang.ada:17051
Date: 2010-12-20T22:03:13+00:00
List-Id: <comp.lang.ada>

Jeffrey Carter <spam.jrcarter.not@spam.not.acm.org> writes:

> The type Flags and the Set_Flags parameters of that type are not
> documented in the spec; if possible, they should be. In particular,
> the effect of the default value for Set_Flags should be described.
>
> The meaning of the expiration parameters, and especially of their
> default values, should be documented. The default of zero would seem
> to mean immediate expirations, which doesn't seem very useful.
>
> The meaning of the Boolean return values from some of the functions
> (which also appear as parameters) is unclear and should be documented.

I think these are "symptoms" of a thin (thinnish) binding. In
particular, the type Expiration and its use is rather non-Ada style. Is
it really the case that the memcached server won't allow you to specify
a retention period greater than 30 days? (just checked -- yes -- well,
the Google Python API says "up to 1 month", close enough I suppose :-).

I don't see why Set appears as two functions & one procedure? Would it
be sensible to say, perhaps,

   procedure Set (....); -- no expiry specified

   procedure Set (....;
                  Expiring_After : Duration);

   procedure Set (....;
                  Expiring_At : Ada.Calendar.Time);


Why is type Connection tagged? I guess you have some expansion plans for
it?!