Re: [http-state] Simple HTTP State Management
Adam Barth <ietf@adambarth.com> Sat, 17 July 2010 23:07 UTC
Return-Path: <ietf@adambarth.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 29ABE3A67FA for <http-state@core3.amsl.com>; Sat, 17 Jul 2010 16:07:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.762
X-Spam-Level:
X-Spam-Status: No, score=-0.762 tagged_above=-999 required=5 tests=[AWL=-0.644, BAYES_20=-0.74, FM_FORGED_GMAIL=0.622]
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 ud7LgeiF72Wh for <http-state@core3.amsl.com>; Sat, 17 Jul 2010 16:07:09 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id A0CE13A6823 for <http-state@ietf.org>; Sat, 17 Jul 2010 16:07:08 -0700 (PDT)
Received: by iwn38 with SMTP id 38so3637741iwn.31 for <http-state@ietf.org>; Sat, 17 Jul 2010 16:07:21 -0700 (PDT)
Received: by 10.231.40.6 with SMTP id i6mr3288156ibe.26.1279408040198; Sat, 17 Jul 2010 16:07:20 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by mx.google.com with ESMTPS id 34sm16898933ibi.6.2010.07.17.16.07.18 (version=SSLv3 cipher=RC4-MD5); Sat, 17 Jul 2010 16:07:19 -0700 (PDT)
Received: by iwn38 with SMTP id 38so3637725iwn.31 for <http-state@ietf.org>; Sat, 17 Jul 2010 16:07:18 -0700 (PDT)
Received: by 10.231.155.206 with SMTP id t14mr3266206ibw.34.1279408038347; Sat, 17 Jul 2010 16:07:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.143.145 with HTTP; Sat, 17 Jul 2010 16:06:58 -0700 (PDT)
In-Reply-To: <4C4234AA.5070502@acm.org>
References: <AANLkTikI3PbdZGtforTKRwzhOo6aWVju0S613arE50eO@mail.gmail.com> <4C4234AA.5070502@acm.org>
From: Adam Barth <ietf@adambarth.com>
Date: Sat, 17 Jul 2010 16:06:58 -0700
Message-ID: <AANLkTik72mFseFWqoJrxj7IVwTVSdV-j6VZxCuS9DMoj@mail.gmail.com>
To: Dave Kristol <dmk@acm.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: Andrew Bortz <abortz@cs.stanford.edu>, http-state <http-state@ietf.org>
Subject: Re: [http-state] Simple HTTP State Management
X-BeenThere: http-state@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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: Sat, 17 Jul 2010 23:07:11 -0000
On Sat, Jul 17, 2010 at 3:54 PM, Dave Kristol <dmk@acm.org> wrote: > On 07/17/2010 05:22 PM, Adam Barth wrote: >> It's good to see various folks sending in proposals for new HTTP state >> management mechanisms. I thought I would throw my hat in the ring >> with some ideas I've been discussing with Andrew Bortz and others: >> >> >> https://docs.google.com/document/pub?id=1l_YcZzF82OJdld5cJX38abSlIwG3dfW37gZTk6PDHwU >> >> I've also included the document inline below. Let me know if you have >> any feedback. > > That's pretty funny. What goes around comes around. In 1995 I proposed > what I think may be a similar mechanism. (See > <http://kristol.org/cookie/session.txt> or .ps, if you prefer.) It's > mentioned in my ACM article, previously mentioned here > (<http://arXiv.org/abs/cs.SE/0105018>). When the state management sub-group > started up, it was one of three proposals we considered, Netscape's cookies > being one of the other two. Great minds think alike? :) Some subtle differences: 1) State-Info looks to be chosen by the server instead of generated randomly by the client. 2) State-Info looks to be scoped to an entire origin server instead of divided by port and scheme. Adam
- [http-state] Simple HTTP State Management Adam Barth
- Re: [http-state] Simple HTTP State Management Adam Barth
- Re: [http-state] Simple HTTP State Management Mark Pauley