[Forces-protocol] Re: Data encoding -- first part

"Joel M. Halpern" <jhalpern@MEGISTO.com> Mon, 18 October 2004 21:44 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26651 for <forces-protocol-web-archive@ietf.org>; Mon, 18 Oct 2004 17:44:31 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJfUk-0002K9-I8 for forces-protocol-web-archive@ietf.org; Mon, 18 Oct 2004 17:57:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJewB-0006DT-Fd; Mon, 18 Oct 2004 17:21:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJeay-00022P-G3 for forces-protocol@megatron.ietf.org; Mon, 18 Oct 2004 16:59:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22779 for <forces-protocol@ietf.org>; Mon, 18 Oct 2004 16:59:00 -0400 (EDT)
Received: from [64.254.114.114] (helo=megisto-e2k.megisto.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJemf-0001Oc-4W for forces-protocol@ietf.org; Mon, 18 Oct 2004 17:11:31 -0400
Received: from JLaptop.megisto.com ([192.168.20.163]) by megisto-e2k.megisto.com with Microsoft SMTPSVC(5.0.2195.6713); Mon, 18 Oct 2004 16:58:22 -0400
Message-Id: <5.1.0.14.0.20041018165715.03523890@mail.megisto.com>
X-Sender: jhalpern@mail.megisto.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 18 Oct 2004 16:58:18 -0400
To: Zsolt Haraszti <zsolt@modularnet.com>, Alan DeKok <alan.dekok@idt.com>
From: "Joel M. Halpern" <jhalpern@MEGISTO.com>
In-Reply-To: <1098132328.2884.250.camel@localhost.localdomain>
References: <41741D78.4070205@idt.com> <468F3FDA28AA87429AD807992E22D07E025791E5@orsmsx408> <002d01c4b50b$1ecc9c10$020aa8c0@wwm1> <1098102734.1042.134.camel@jzny.localdomain> <1098113089.2364.12.camel@localhost.localdomain> <1098115003.2884.67.camel@localhost.localdomain> <4173FB88.1000008@idt.com> <1098126011.2884.162.camel@localhost.localdomain> <41741D78.4070205@idt.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-OriginalArrivalTime: 18 Oct 2004 20:58:22.0188 (UTC) FILETIME=[33F6DAC0:01C4B555]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>, ram.gopal@nokia.com, forces-protocol@ietf.org, "Yang, Lily L" <lily.l.yang@intel.com>, Jamal Hadi Salim <hadi@znyx.com>, "Steven Blake (petri-meat)" <slblake@petri-meat.com>, Ellen M Deleganes <ellen.m.deleganes@intel.com>, Weiming Wang <wmwang@mail.hzic.edu.cn>
Subject: [Forces-protocol] Re: Data encoding -- first part
X-BeenThere: forces-protocol@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: forces-protocol <forces-protocol.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/forces-protocol>, <mailto:forces-protocol-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/forces-protocol>
List-Post: <mailto:forces-protocol@ietf.org>
List-Help: <mailto:forces-protocol-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/forces-protocol>, <mailto:forces-protocol-request@ietf.org?subject=subscribe>
Sender: forces-protocol-bounces@ietf.org
Errors-To: forces-protocol-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8

Why not just declare that structs start with their length.  Then we can 
declare that an array consists of its element count (or length and element 
count) followed by the representation of its contents.  [Ignoring for the 
moment the issue of dense vs sparse packing, subscript representation, etc.]

Yours,
Joel

At 04:45 PM 10/18/2004 -0400, Zsolt Haraszti wrote:
>This is another trade-off issue.  You are absolutely right, inserting
>the size info in front of each struct can be very useful, especially if
>it is a variable size struct.  We will have this in ARRAYs, not
>part of the struct itself, but part of the ARRAY encoding.
>That does not help when the STRUCT is embedded in another struct though.


_______________________________________________
Forces-protocol mailing list
Forces-protocol@ietf.org
https://www1.ietf.org/mailman/listinfo/forces-protocol