RE: [NGO] NETCONF Data types

Hi Sharon,

64-bit integers are crucial e.g., for applications dealing with precise
timestamps. Of course, an appropriate integer range should be used in
each context. In my opinion, the integer datatypes defined by the W3C
Datatype Library provide a very reasonable selection and I see no point
in reducing this choice.

Lada

Sharon Chisholm píše v Po 07. 01. 2008 v 09:07 -0500:
> Hi
> 
> If it is define with length=64, then you know you can't read it and
> ignore it. If it is defined with length=32, the you know you can read it
> and do.
> 
> Sharon 
> 
> -----Original Message-----
> From: Juergen Schoenwaelder
> [mailto:j.schoenwaelder@jacobs-university.de] 
> Sent: Monday, January 07, 2008 9:05 AM
> To: Chisholm, Sharon (CAR:ZZ00)
> Cc: ngo@ietf.org
> Subject: Re: [NGO] NETCONF Data types
> 
> On Mon, Jan 07, 2008 at 08:47:46AM -0500, Sharon Chisholm wrote:
>  
> > By the way, I chatted with one of my application folks about the 32 
> > versus 64 bit integer question and he indicated that he can't handle 
> > 64 bit integers in his application so does want to when they he might 
> > expect them. In that case, a better approach is likely a complex type 
> > which gives length and value. This way if you handle all lengths, you 
> > just need to look at the value field.
> 
> I don't understand the proposal or how what I understand helps someone
> who can't deal with 64 bit numbers.
> 
> /js
> 
-- 
Ladislav Lhotka, CESNET
PGP Key ID: E74E8C0C

_______________________________________________
NGO mailing list
NGO@ietf.org
https://www1.ietf.org/mailman/listinfo/ngo