Re: [mmox] Representing Number Types [Was: Re: Details proposal]
Jon Watte <jwatte@gmail.com> Wed, 25 February 2009 19:20 UTC
Return-Path: <jwatte@gmail.com>
X-Original-To: mmox@core3.amsl.com
Delivered-To: mmox@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 484E428C2B0 for <mmox@core3.amsl.com>; Wed, 25 Feb 2009 11:20:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.501
X-Spam-Level:
X-Spam-Status: No, score=-2.501 tagged_above=-999 required=5 tests=[AWL=0.098, BAYES_00=-2.599]
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 fQ4tGpaUsKal for <mmox@core3.amsl.com>; Wed, 25 Feb 2009 11:20:03 -0800 (PST)
Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28]) by core3.amsl.com (Postfix) with ESMTP id 4E4CB28C2AC for <mmox@ietf.org>; Wed, 25 Feb 2009 11:20:03 -0800 (PST)
Received: by yx-out-2324.google.com with SMTP id 8so202549yxm.49 for <mmox@ietf.org>; Wed, 25 Feb 2009 11:20:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=2jBzpoWZz5cN0ZqQ0Kq3gcqpHRBlT/xYL9nIWKWFsf8=; b=f861yNqf0mkwGKXSx7o33UIS2REBrBcVULWJwDUSCZvVf0rtqMyk9XWiEWoHXaVBiQ mkqcegONLvNQXI1huaKg9iG3KAilz7ozGdcMMCd8CEMLfXaa+5hOOeWfhKzWmhcpaHFL vJbm6KUgnmgh66OncJlBywkLxlyMui0VDQNuE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=x508VC1BpfUtHQNHsVC4yGWQ6gTEel5C5BxXb8V7G03sz65VTNAl9auHHIaf3q8F4Y pL3MjB2jbMBgVUIo5Uw8o+H5HAny69WwmGN2N1HH70NTEAQCnwLLoiyhpsl481eedEy3 zkLYxMjm+wBg2TNR+QYMn0a8LM9+F1t1X4ys4=
Received: by 10.100.142.4 with SMTP id p4mr856468and.23.1235589622597; Wed, 25 Feb 2009 11:20:22 -0800 (PST)
Received: from ?192.168.168.111? (smtp.forterrainc.com [208.64.184.34]) by mx.google.com with ESMTPS id c1sm9097321ana.0.2009.02.25.11.20.21 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 25 Feb 2009 11:20:22 -0800 (PST)
Message-ID: <49A599F4.3020908@gmail.com>
Date: Wed, 25 Feb 2009 11:20:20 -0800
From: Jon Watte <jwatte@gmail.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: "Meadhbh Hamrick (Infinity)" <infinity@lindenlab.com>
References: <ebe4d1860902241743v16a1be91tc70c265fcafd4586@mail.gmail.com> <1E712A17-6D23-471C-A827-CD86C1EDE59D@lindenlab.com> <49A5955B.8000401@gmail.com> <AACE1007-FDF1-4FEB-9BCE-2F2701540D24@lindenlab.com>
In-Reply-To: <AACE1007-FDF1-4FEB-9BCE-2F2701540D24@lindenlab.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: mmox@ietf.org
Subject: Re: [mmox] Representing Number Types [Was: Re: Details proposal]
X-BeenThere: mmox@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Massively Multi-participant Online Games and Applications <mmox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmox>
List-Post: <mailto:mmox@ietf.org>
List-Help: <mailto:mmox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Feb 2009 19:20:04 -0000
Meadhbh Hamrick (Infinity) wrote: > - or is it okay for me to say.. "if you connect to Second Life, i > will insist that integers are 32 bits." and for OSGrid to say "if you > connect to OSGrid, i will insist that integers are 64 bits." I don't think that's smart, because sometimes an integer value only needs to be one byte. In OLIVE we specify integers with a bit-precision representation -- a 13-bit int is nothing special to us. Our internal IDL compiles to structures that arrange and pad integers based on declared size. We don't do integers bigger than 64 bits, though. I'm prepared to relax this to 'integers are one of the basic types' (8, 16, 32 or 64 bits, signed or unsigned) for purposes of interoperability, but I think that specifying integer ranges in the declaration of messages is necessary, or you'll have to treat every integer field as possibly being the worst case (64 bits signed). Sincerely, jw
- [mmox] Details proposal Catherine Pfeffer
- Re: [mmox] Details proposal Jon Watte
- [mmox] Changing the Name [was: Re: Details propos… Meadhbh Hamrick (Infinity)
- [mmox] Representing Number Types [Was: Re: Detail… Meadhbh Hamrick (Infinity)
- Re: [mmox] Representing Number Types [Was: Re: De… Dan Olivares
- Re: [mmox] Changing the Name [was: Re: Details pr… Dan Olivares
- Re: [mmox] Representing Number Types [Was: Re: De… Meadhbh Hamrick (Infinity)
- Re: [mmox] Representing Number Types [Was: Re: De… Jon Watte
- Re: [mmox] Representing Number Types [Was: Re: De… Meadhbh Hamrick (Infinity)
- Re: [mmox] Representing Number Types [Was: Re: De… Jon Watte