Re: [http-state] Updated draft

Adam Barth <ietf@adambarth.com> Mon, 17 August 2009 18:52 UTC

Return-Path: <adam@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 E991528C2E7 for <http-state@core3.amsl.com>; Mon, 17 Aug 2009 11:52:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.799
X-Spam-Level:
X-Spam-Status: No, score=-1.799 tagged_above=-999 required=5 tests=[AWL=0.178, BAYES_00=-2.599, 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 fUVAnYL58csY for <http-state@core3.amsl.com>; Mon, 17 Aug 2009 11:52:59 -0700 (PDT)
Received: from mail-vw0-f196.google.com (mail-vw0-f196.google.com [209.85.212.196]) by core3.amsl.com (Postfix) with ESMTP id 2CF8028C2E9 for <http-state@ietf.org>; Mon, 17 Aug 2009 11:52:59 -0700 (PDT)
Received: by vws34 with SMTP id 34so2776559vws.31 for <http-state@ietf.org>; Mon, 17 Aug 2009 11:53:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.43.196 with SMTP id x4mr5210151vce.16.1250535181106; Mon, 17 Aug 2009 11:53:01 -0700 (PDT)
In-Reply-To: <4A8996DE.4030905@gmx.de>
References: <7789133a0908151008p35ff30e6w2761368fe70d41a6@mail.gmail.com> <7789133a0908161032l2265ce5fg966c434f1b05aa64@mail.gmail.com> <alpine.DEB.2.00.0908161952060.13789@yvahk2.pbagnpgbe.fr> <7789133a0908161131s5741d457q812b5e4213452054@mail.gmail.com> <alpine.DEB.2.00.0908162035140.13789@yvahk2.pbagnpgbe.fr> <4A889417.9020709@gmail.com> <alpine.DEB.2.00.0908170929100.22132@yvahk2.pbagnpgbe.fr> <7789133a0908170853r5a81b84cu1308049256f51d2c@mail.gmail.com> <7789133a0908170908r4e3e8d30v7187bbf67f76b95c@mail.gmail.com> <4A8996DE.4030905@gmx.de>
From: Adam Barth <ietf@adambarth.com>
Date: Mon, 17 Aug 2009 11:52:41 -0700
Message-ID: <7789133a0908171152q5cdd97beia9e4034148e63e0e@mail.gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Daniel Stenberg <daniel@haxx.se>, http-state <http-state@ietf.org>
Subject: Re: [http-state] Updated draft
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: Mon, 17 Aug 2009 18:53:00 -0000

On Mon, Aug 17, 2009 at 10:43 AM, Julian Reschke<julian.reschke@gmx.de> wrote:
> Why would you have to pick an ordering?
>
> In Java, I might just drop then into a HashSet, and never worry about
> ordering...

In the end you have to serialize the set of cookies you transmit to
the server into a sequence of bytes for the Cookie header.  When you
do this, you have to pick an ordering for that sequence of bytes.  Of
course, you can pick a different order each time you serialize, but
that seems inferior to matching the behavior of 99% of the market.

Adam