Hi Ben,
I've just tried your instructions and it builds and runs ok. Many thanks!
Ben
On 3 July 2012 21:43, Ben Noordhuis i...@bnoordhuis.nl wrote:
On Tue, Jul 3, 2012 at 3:02 PM, Ben Noordhuis i...@bnoordhuis.nl wrote:
On Tue, Jul 3, 2012 at 2:02 PM, Ben Short b...@benshort.co.uk wrote
Hi,
Is it possible to run Node JS 0.8.0 on FreeBSD?
I ask because libuv doesn't start that FreeBSD is a supported operating
system and Node JS no uses libuv.
Thanks
Ben
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
haven't had a need yet. Gimme a minute...
On Thu, Jun 21, 2012 at 2:14 PM, Ben Short b...@benshort.co.uk wrote:
Nathan,
I'm trying this code:
var eventTimeStamp = buffer.readUInt64BE(0);
but get the following error:
var eventTimeStamp = buffer.readUInt64BE(0
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
-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
:
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)
On Thu, Jun 21, 2012 at 2:48 PM, Ben Short b...@benshort.co.uk wrote:
After searching this group I got
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
On 21 June 2012 22:06, Ben Short b...@benshort.co.uk
