Re: Reading a unsigned 64bit integer from a buffer.

2,605 views
Skip to first unread message

Ben Short

unread,
Jun 21, 2012, 3:48:40 PM6/21/12
to nod...@googlegroups.com
After searching this group I got it to work using the long class [1]

code snipit:

var Long = require('./long.js').Long;

var high = buffer.readUInt32BE(0);
var low = buffer.readUInt32BE(4); 

var l = Long.fromBits(low, high);

var timestamp = l.toNumber();


[1] https://github.com/mongodb/js-bson/blob/master/lib/bson/long.js

On Thursday, June 21, 2012 8:15:05 PM UTC+1, Ben Short wrote:
Hi, 

I'm trying out nodejs as a TCP server. The client server protocol is binary and the first value is a unsigned 64bit integer. The actual value in this 8 byte's is a unix epoch such as 1340304234643. The bytes are in network byte order/big endian.

Is there anyway that I'm going to be able to read this value in nodejs?

Thanks

Ben

Tim Caswell

unread,
Jun 21, 2012, 4:04:22 PM6/21/12
to nod...@googlegroups.com
Keep in mind that you'll lose precision when converting it to a native javascript number.  JS numbers are defined to be double floats. (though I head long type is coming in future JS)

--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Nathan Rajlich

unread,
Jun 21, 2012, 4:52:37 PM6/21/12
to nod...@googlegroups.com
My "ref"[1] module can do this. It extends Buffer.prototype with the missing {read,write}{U}Int64{LE,BE] functions by calling into native functions. It can accept Strings with big integers inside of it and it will strtoll or strtoull the value in C-land. It also returns Strings when the value being returned is outside the range of a valid JS Number.

Ben Short

unread,
Jun 21, 2012, 5:06:26 PM6/21/12
to nod...@googlegroups.com
Thanks Nathan that looks like just what I'm after.

Ben Short

unread,
Jun 21, 2012, 5:14:43 PM6/21/12
to nod...@googlegroups.com
Nathan,

I'm trying this code:

   var eventTimeStamp = buffer.readUInt64BE(0);

but get the following error:

   var eventTimeStamp = buffer.readUInt64BE(0);
                                 ^
   TypeError: Object

What am I missing?

Ben

Nathan Rajlich

unread,
Jun 21, 2012, 5:23:48 PM6/21/12
to nod...@googlegroups.com
Ben, can you tell me what "ref.endianness" is reporting on your machine? If it's "LE" then I'll need to make an update to "ref" to support the non-native-endian read/write functions. It's been on my todo list, just haven't had a need yet. Gimme a minute...

Nathan Rajlich

unread,
Jun 21, 2012, 6:12:41 PM6/21/12
to nod...@googlegroups.com
Ok Ben, try out v0.0.18 of ref. It adds the "non-native-endianness" version of those read/write functions as well. Cheers!

Ben Short

unread,
Jun 22, 2012, 3:20:24 AM6/22/12
to nod...@googlegroups.com
Nathan, 

ref.endianness reports LE.

I upgraded to v 0.0.18 and the code works as expected.

Many thanks

Ben
Reply all
Reply to author
Forward
0 new messages