Re: FW: [Rfid] SLRRP Vendor Extensions

Margaret Wasserman <margaret@thingmagic.com> Fri, 22 July 2005 16:12 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dw08K-0002ez-SP; Fri, 22 Jul 2005 12:12:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dw08J-0002ZU-5V for rfid@megatron.ietf.org; Fri, 22 Jul 2005 12:12:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29121 for <rfid@ietf.org>; Fri, 22 Jul 2005 12:12:16 -0400 (EDT)
Received: from [204.9.221.21] (helo=thingmagic.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dw0cZ-0003dq-2f for rfid@ietf.org; Fri, 22 Jul 2005 12:43:36 -0400
Received: from [66.30.121.250] (account margaret HELO [192.168.1.105]) by thingmagic.com (CommuniGate Pro SMTP 4.1.8) with ESMTP-TLS id 448740; Fri, 22 Jul 2005 12:06:10 -0400
Mime-Version: 1.0
Message-Id: <p062007d1bf06c9caadb0@[192.168.1.105]>
In-Reply-To: <1122042525.10159.77.camel@avon>
References: <200507211720.j6LHKCx4004859@mail.intelleflex.com> <1122042525.10159.77.camel@avon>
Date: Fri, 22 Jul 2005 12:11:05 -0400
To: Peter Spreadborough <pspreadborough@revasystems.com>, Suresh Bhaskaran <sbhaskaran@intelleflex.com>
From: Margaret Wasserman <margaret@thingmagic.com>
Subject: Re: FW: [Rfid] SLRRP Vendor Extensions
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: rfid@ietf.org
X-BeenThere: rfid@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Control and Access of Infrastructure for RFID Operations Discussion List <rfid.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rfid>, <mailto:rfid-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/rfid>
List-Post: <mailto:rfid@lists.ietf.org>
List-Help: <mailto:rfid-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rfid>, <mailto:rfid-request@lists.ietf.org?subject=subscribe>
Sender: rfid-bounces@lists.ietf.org
Errors-To: rfid-bounces@lists.ietf.org

At 10:28 AM -0400 7/22/05, Peter Spreadborough wrote:
>Setting the V bit will indicate the presence of the VendorID field in
>the message header. If the V bit is not set then the VendorID will not
>be present. On receipt of a message with the V bit set an implementation
>may decide to accept or reject that message.

BTW, once you start having binary fields that are or are not present 
based on the value of other bits, you lose one of the advantages that 
David Husak claimed for a binary format -- that you can just put the 
received buffer in memory and access fields directly without the need 
to parse anything

The "slap it in memory and just access it" plan also runs amok of 
other issues such as alignment constraints, data packing issues and 
endianness.  All of those can be worked around by proper coding, but 
it is an implementation consideration whether handling straight 
binary access will/won't be cheaper (in time, code size or runtime 
memory use) than parsing the binary data into internal structures 
upon receipt.  If you add variable-length or conditional fields, 
you'll quickly determine that parsing it once is much more efficient 
(and less prone to small incompatibility bugs all over your code).

Margaret


_______________________________________________
Rfid mailing list
Rfid@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/rfid