Re: [http-state] draft-abarth-cake-00 posted

David Morris <dwm@xpasc.com> Tue, 24 August 2010 04:22 UTC

Return-Path: <dwm@xpasc.com>
X-Original-To: http-state@core3.amsl.com
Delivered-To: http-state@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E644A3A681D for <http-state@core3.amsl.com>; Mon, 23 Aug 2010 21:22:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.307
X-Spam-Level:
X-Spam-Status: No, score=-3.307 tagged_above=-999 required=5 tests=[AWL=-0.708, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fj6M0OWavrqu for <http-state@core3.amsl.com>; Mon, 23 Aug 2010 21:22:51 -0700 (PDT)
Received: from mail.xpasc.com (mail.xpasc.com [68.164.244.189]) by core3.amsl.com (Postfix) with ESMTP id 35FB03A6405 for <http-state@ietf.org>; Mon, 23 Aug 2010 21:22:51 -0700 (PDT)
Received: from bslepgate.xpasc.com (localhost.localdomain [127.0.0.1]) by bslepgate.xpasc.com (Postfix-out) with ESMTP id 39780101836 for <http-state@ietf.org>; Mon, 23 Aug 2010 21:23:25 -0700 (PDT)
X-Propel-Return-Path: <dwm@xpasc.com>
Received: from mail.xpasc.com ([10.1.2.88]) by [127.0.0.1] ([127.0.0.1]) (port 7027) (Abaca EPG outproxy filter 3.1.2.exported $Rev: 9262 $) id iz6Ura8o4np0; Mon, 23 Aug 2010 21:23:25 -0700
Received: from xpasc.com (egate.xpasc.com [10.1.2.49]) by bslepgate.xpasc.com (Postfix-out) with ESMTP id EA89610058B for <http-state@ietf.org>; Mon, 23 Aug 2010 21:23:24 -0700 (PDT)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id o7O4NOjs019897 for <http-state@ietf.org>; Mon, 23 Aug 2010 21:23:24 -0700
Date: Mon, 23 Aug 2010 21:23:24 -0700
From: David Morris <dwm@xpasc.com>
To: http-state <http-state@ietf.org>
In-Reply-To: <8B0A9FCBB9832F43971E38010638454F03EF266B47@SISPE7MB1.commscope.com>
Message-ID: <Pine.LNX.4.64.1008232120120.16056@egate.xpasc.com>
References: <AANLkTi=c9i=gNFspyf4NC0Cm423JtH0v4FHR18Lm_GrB@mail.gmail.com> <F79FCB2B-2F28-46D0-AFB9-80875E27A9A2@apple.com> <8B0A9FCBB9832F43971E38010638454F03EF266B47@SISPE7MB1.commscope.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Propel-ID: iz6Ura8o4np0
Subject: Re: [http-state] draft-abarth-cake-00 posted
X-BeenThere: http-state@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: http-state <http-state@ietf.org>
List-Id: Discuss HTTP State Management Mechanism <http-state.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/http-state>, <mailto:http-state-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/http-state>
List-Post: <mailto:http-state@ietf.org>
List-Help: <mailto:http-state-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-state>, <mailto:http-state-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Aug 2010 04:22:52 -0000

On Tue, 24 Aug 2010, Thomson, Martin wrote:

> But to give it a sensible name would be...sensible...and a little dull.
> That's contrary to a well-established tradition (YMMV).
> 
> Given that this provides less state than a cookie, "wafer" might be a
> better use of the prevailing analogy.


hmmm ... I like wafer ... because it is a multiple use word which is
used in electronics for various layer like things. Frankly, everytime
I read 'cake' I have to to a mental search/translate to associate it
with cookie.  In my experience, a cake is a much more heavyweight
concept than cookie.