Return-Path: X-Original-To: apmail-zest-dev-archive@minotaur.apache.org Delivered-To: apmail-zest-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EE14F17566 for ; Thu, 21 May 2015 10:29:23 +0000 (UTC) Received: (qmail 29428 invoked by uid 500); 21 May 2015 10:29:23 -0000 Delivered-To: apmail-zest-dev-archive@zest.apache.org Received: (qmail 29392 invoked by uid 500); 21 May 2015 10:29:23 -0000 Mailing-List: contact dev-help@zest.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@zest.apache.org Delivered-To: mailing list dev@zest.apache.org Received: (qmail 29378 invoked by uid 99); 21 May 2015 10:29:23 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 May 2015 10:29:23 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 1161AC7316 for ; Thu, 21 May 2015 10:29:23 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.1 X-Spam-Level: X-Spam-Status: No, score=-0.1 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id snJfT1w0pc9c for ; Thu, 21 May 2015 10:29:15 +0000 (UTC) Received: from mail-la0-f43.google.com (mail-la0-f43.google.com [209.85.215.43]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 1C39D45498 for ; Thu, 21 May 2015 10:29:15 +0000 (UTC) Received: by lagv1 with SMTP id v1so99816258lag.3 for ; Thu, 21 May 2015 03:29:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=P3BPcCJ9gPuG+J5z36WAlj2N6SeCzUnmJsoM5Gdqa0M=; b=iwlS1aSGcZ2IZKD5DQA91ObpOgQ43UMm6v3oi+UaSvz79nnzt0Y+LK0trBqGmgsL3e 5jSXG+o2gOlGYrhmeM0KcXymMrv0r5mh7WFPpQKFM3uVa+e8rhisg9q/RBmYstwWWEzT 5MCrhUhz5u8M3VN0aAuiIVMvXT/mgHF64/lVLQ27E1+CiiLv9mpKTCBURgztMrnXUQuv zYMhBBRtJVBMclxNNITrf3hVN2wjpS7jUWLJWSX8zYgV+lksGJfm/dZ41Rgs3lIxA0RM 0afdpbi0taIjk9bSg0zPjKK+Ka7Ho5X66y9kUxmGgj/P1HBtuJPfQSqON3O5pL4Qb4jJ b38A== X-Received: by 10.152.5.134 with SMTP id s6mr1511720las.99.1432204148411; Thu, 21 May 2015 03:29:08 -0700 (PDT) Received: from [192.168.0.134] ([87.51.7.222]) by mx.google.com with ESMTPSA id ln6sm5187162lac.45.2015.05.21.03.29.06 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 May 2015 03:29:07 -0700 (PDT) Message-ID: <555DB37D.7020900@gmail.com> Date: Thu, 21 May 2015 12:29:17 +0200 From: =?UTF-8?B?S2VudCBTw7hsdnN0ZW4=?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: dev@zest.apache.org Subject: Re: ZEST-23 References: <555DA265.1000605@nosphere.org> <555DA85D.8010908@nosphere.org> <555DB298.6080707@nosphere.org> In-Reply-To: <555DB298.6080707@nosphere.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit b. Keep the Map serialization for now as it is. c. Plan the change for 3.0 later in the year, giving us a bit of time to figure out the migration. Agreed a. Change NamedAssociation to be serialized in "object" form now. You mean change the deserializer to expect object form, right? /Kent Den 21-05-2015 kl. 12:25 skrev Paul Merlin: > Niclas Hedhman a écrit : >> On Thu, May 21, 2015 at 5:41 PM, Paul Merlin wrote: >>> Looking at it today I don't know why key order should matter. >>> I'd say that having more idiomatic JSON would make usage less contrived, >>> which would be a good thing. >> I agree that is very desirable, and it is now mostly a matter of how to >> handle data migration, if we go with Kent's advice. >> >> Obviously no one uses NamedAssociation, since I can't see that this ever >> worked, as there is a mismatch (serialize object and deserialize an array) >> at the moment. >> >> Kent, good to know that JS is cool with that. >> >> The quickest fix was to change the Serializer to match the Deserializer for >> NamedAssociations. And I am committing that version shortly in a separate >> branch... >> >> But, while discussing this, I think we should do this; >> >> a. Change NamedAssociation to be serialized in "object" form now. >> b. Keep the Map serialization for now as it is. >> c. Plan the change for 3.0 later in the year, giving us a bit of time to >> figure out the migration. >> >> WDYT? > Sounds like a good plan. > >