Re: [nodejs] Desktop apps with Node.js
Currently we're developing on the 'cef' branch. Once it's stable we'll switch it to master. How much work does it need to get stable Roger? Do you still change libuv and node to merge CEF's V8 with node's V8? If you don't change node, I will be able to use your modified CEF with AppJS. -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Re: Reading a unsigned 64bit integer from a buffer.
Nathan,
ref.endianness reports LE.
I upgraded to v 0.0.18 and the code works as expected.
Many thanks
Ben
On 21 June 2012 23:12, Nathan Rajlich nat...@tootallnate.net wrote:
Ok Ben, try out v0.0.18 of ref. It adds the non-native-endianness
version of those read/write functions as well. Cheers!
On Thu, Jun 21, 2012 at 2:23 PM, Nathan Rajlich nat...@tootallnate.netwrote:
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...
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);
^
TypeError: Object
What am I missing?
Ben
On 21 June 2012 22:06, Ben Short b...@benshort.co.uk wrote:
Thanks Nathan that looks like just what I'm after.
On 21 June 2012 21:52, Nathan Rajlich nat...@tootallnate.net wrote:
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.
Cheers!
1: https://github.com/TooTallNate/ref
On Thu, Jun 21, 2012 at 1:04 PM, Tim Caswell t...@creationix.comwrote:
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.ukwrote:
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
--
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
--
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
--
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
--
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
--
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
--
Job Board: http://jobs.nodejs.org/
Posting
Re: [nodejs] Re: API changes from 0.6 to 0.8
The goal is to have a module compatible with both 0.6 and 0.8, not one for each
version.
--
Diogo Resende
On Friday, June 22, 2012 at 2:37 , Dominic Tarr wrote:
you can set what version of node a module is for in the package.json
engines: { node : 0.6 }
for example. this does mean you'll have two versions of the code,
feature detection may be easier to maintain. you choice.
see `npm help json`
On Fri, Jun 22, 2012 at 12:14 AM, Roly Fentanes roly...@gmail.com
(mailto:roly...@gmail.com) wrote:
I'm in a similar situation with a module I wrote. And I think I'll just
write a note in the readme specifying which version should be installed for
node v0.6.x.
On Thursday, June 21, 2012 2:35:15 AM UTC-7, Diogo Resende wrote:
Hi,
I have a module (node-rack) to abstract the cluster module. It was built
for 0.6 and I want to be able to support 0.8 too but not dropping 0.6
support. I noticed for example that `kill()` was renamed to `destroy()`. I
think this can be easy to detect but what about events? `death`event was
changed to `exit`.
Is there a way to know what events an object supports or should I just
check the node version (using process.version.node) and do my changes from
there?
I would prefer the first option as it's similar to feature detection. This
way I would just check for available methods and events and use the
preferred (and available) ones.
--
Diogo Resende
--
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 nodejs@googlegroups.com
(mailto:nodejs@googlegroups.com)
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
(mailto:nodejs+unsubscr...@googlegroups.com)
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
--
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 nodejs@googlegroups.com
(mailto:nodejs@googlegroups.com)
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
(mailto:nodejs+unsubscr...@googlegroups.com)
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
--
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] forever and cpu usage
Hi, I run my node with forever, it works quite well, got two questions: 1) at any given time, there are two node running, that's normal? 3) cpu sometimes goes up to 90-100% when the traffic is high, then goes back to less than 10 quickly, is this normal? is there a way to check which part goes so high? angelo -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Re: Sticky sessions using the new cluster API?
Hi, I'm trying to work on this problem. I have an npm that extends node-http-proxy to provide round-robin and sticky-sessions support, I built an option to use Redis as the persistent memory store so that you could use cluster, but there's a bug somewhere so I might need help fixing that. The default in-process memory option works fine. https://github.com/paulbjensen/satellite Regards, Paul Jensen On Tuesday, June 19, 2012 5:34:42 AM UTC+1, dhruvbird wrote: Is it possible to have sticky sessions using the new cluster API? Some custom logic such as a cookie based solution? Something similar to nginx sticky module? -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Unable to compile node v0.8 RC7 on ARM (Beaglebone)
On Fri, Jun 22, 2012 at 3:39 PM, Ewan Leith ewan.le...@gmail.com wrote:
Hi all, I'm trying to compile node v0.8 rc7 on my beaglebone, and the
configure script it falling over. It does work fine on the 0.6 branch. Has
anyone built node v0.8 or v0.7 on ARM?
Running configure (with or without -det-cpu=arm) gives the following output:
./configure --dest-cpu=arm
{ 'target_defaults': { 'cflags': [],
'default_configuration': 'Release',
'defines': [],
'include_dirs': [],
'libraries': []},
'variables': { 'host_arch': 'arm',
'node_install_npm': 'true',
'node_install_waf': 'true',
'node_prefix': '',
'node_shared_openssl': 'false',
'node_shared_v8': 'false',
'node_shared_zlib': 'false',
'node_use_dtrace': 'false',
'node_use_etw': 'false',
'node_use_openssl': 'true',
'strict_aliasing': 'true',
'target_arch': 'arm',
'v8_use_snapshot': 'true'}}
creating ./config.gypi
creating ./config.mk
Traceback (most recent call last):
File tools/gyp_node, line 58, in module
run_gyp(gyp_args)
File tools/gyp_node, line 18, in run_gyp
rc = gyp.main(args)
File ./tools/gyp/pylib/gyp/__init__.py, line 471, in main
options.circular_check)
File ./tools/gyp/pylib/gyp/__init__.py, line 111, in Load
depth, generator_input_info, check, circular_check)
File ./tools/gyp/pylib/gyp/input.py, line 2289, in Load
depth, check)
File ./tools/gyp/pylib/gyp/input.py, line 433, in LoadTargetBuildFile
includes, depth, check)
File ./tools/gyp/pylib/gyp/input.py, line 387, in LoadTargetBuildFile
build_file_path)
File ./tools/gyp/pylib/gyp/input.py, line 984, in
ProcessVariablesAndConditionsInDict
ProcessConditionsInDict(the_dict, is_late, variables, build_file)
File ./tools/gyp/pylib/gyp/input.py, line 861, in
ProcessConditionsInDict
variables, build_file)
File ./tools/gyp/pylib/gyp/input.py, line 1010, in
ProcessVariablesAndConditionsInDict
build_file)
File ./tools/gyp/pylib/gyp/input.py, line 1025, in
ProcessVariablesAndConditionsInList
ProcessVariablesAndConditionsInDict(item, is_late, variables,
build_file)
File ./tools/gyp/pylib/gyp/input.py, line 1010, in
ProcessVariablesAndConditionsInDict
build_file)
File ./tools/gyp/pylib/gyp/input.py, line 1025, in
ProcessVariablesAndConditionsInList
ProcessVariablesAndConditionsInDict(item, is_late, variables,
build_file)
File ./tools/gyp/pylib/gyp/input.py, line 984, in
ProcessVariablesAndConditionsInDict
ProcessConditionsInDict(the_dict, is_late, variables, build_file)
File ./tools/gyp/pylib/gyp/input.py, line 861, in
ProcessConditionsInDict
variables, build_file)
File ./tools/gyp/pylib/gyp/input.py, line 984, in
ProcessVariablesAndConditionsInDict
ProcessConditionsInDict(the_dict, is_late, variables, build_file)
File ./tools/gyp/pylib/gyp/input.py, line 842, in
ProcessConditionsInDict
if eval(ast_code, {'__builtins__': None}, variables):
File string, line 1, in module
NameError: name 'armv7' is not defined while evaluating condition 'armv7==1'
in /tmp/node-v0.8.0/deps/v8/tools/gyp/v8.gyp while loading dependencies of
/tmp/node-v0.8.0/node.gyp while trying to load /tmp/node-v0.8.0/node.gyp
Hacking deps/v8/tools/gyp/v8.gyp to just remove the condition that it's
complaining about at line 997, lets the build continue and complete, but it
then crashes when built (probably because I'm excluding relevant switches to
gcc by changing the configure output).
The section of v8.gyp is around line 149:
'conditions': [
['armv7==1', {
Has anyone built node v0.8 or v0.7 on ARM or have some ideas of how to
resolve this?
Gah, I'm still waiting for my BeagleBone.
Does it work when you add `'armv7%':'1'` (sans backticks) to the
variables section of config.gypi or common.gypi?
--
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Unable to compile node v0.8 RC7 on ARM (Beaglebone)
Thanks Ben, I added armv7 then it started complaining about arm_neon, so
I've added that too, to deps/v8/build/common.gypi
I've added these 2 lines at the top, just inside the variables section:
'armv7%':'1',
'arm_neon%':'1',
configure completes now, so I'll try a straight make without any additional
compiler flags and see what happens.
Thanks,
Ewan
On Friday, 22 June 2012 14:51:29 UTC+1, Ben Noordhuis wrote:
On Fri, Jun 22, 2012 at 3:39 PM, Ewan Leith wrote:
Hi all, I'm trying to compile node v0.8 rc7 on my beaglebone, and the
configure script it falling over. It does work fine on the 0.6 branch.
Has
anyone built node v0.8 or v0.7 on ARM?
Running configure (with or without -det-cpu=arm) gives the following
output:
./configure --dest-cpu=arm
{ 'target_defaults': { 'cflags': [],
'default_configuration': 'Release',
'defines': [],
'include_dirs': [],
'libraries': []},
'variables': { 'host_arch': 'arm',
'node_install_npm': 'true',
'node_install_waf': 'true',
'node_prefix': '',
'node_shared_openssl': 'false',
'node_shared_v8': 'false',
'node_shared_zlib': 'false',
'node_use_dtrace': 'false',
'node_use_etw': 'false',
'node_use_openssl': 'true',
'strict_aliasing': 'true',
'target_arch': 'arm',
'v8_use_snapshot': 'true'}}
creating ./config.gypi
creating ./config.mk
Traceback (most recent call last):
File tools/gyp_node, line 58, in module
run_gyp(gyp_args)
File tools/gyp_node, line 18, in run_gyp
rc = gyp.main(args)
File ./tools/gyp/pylib/gyp/__init__.py, line 471, in main
options.circular_check)
File ./tools/gyp/pylib/gyp/__init__.py, line 111, in Load
depth, generator_input_info, check, circular_check)
File ./tools/gyp/pylib/gyp/input.py, line 2289, in Load
depth, check)
File ./tools/gyp/pylib/gyp/input.py, line 433, in
LoadTargetBuildFile
includes, depth, check)
File ./tools/gyp/pylib/gyp/input.py, line 387, in
LoadTargetBuildFile
build_file_path)
File ./tools/gyp/pylib/gyp/input.py, line 984, in
ProcessVariablesAndConditionsInDict
ProcessConditionsInDict(the_dict, is_late, variables, build_file)
File ./tools/gyp/pylib/gyp/input.py, line 861, in
ProcessConditionsInDict
variables, build_file)
File ./tools/gyp/pylib/gyp/input.py, line 1010, in
ProcessVariablesAndConditionsInDict
build_file)
File ./tools/gyp/pylib/gyp/input.py, line 1025, in
ProcessVariablesAndConditionsInList
ProcessVariablesAndConditionsInDict(item, is_late, variables,
build_file)
File ./tools/gyp/pylib/gyp/input.py, line 1010, in
ProcessVariablesAndConditionsInDict
build_file)
File ./tools/gyp/pylib/gyp/input.py, line 1025, in
ProcessVariablesAndConditionsInList
ProcessVariablesAndConditionsInDict(item, is_late, variables,
build_file)
File ./tools/gyp/pylib/gyp/input.py, line 984, in
ProcessVariablesAndConditionsInDict
ProcessConditionsInDict(the_dict, is_late, variables, build_file)
File ./tools/gyp/pylib/gyp/input.py, line 861, in
ProcessConditionsInDict
variables, build_file)
File ./tools/gyp/pylib/gyp/input.py, line 984, in
ProcessVariablesAndConditionsInDict
ProcessConditionsInDict(the_dict, is_late, variables, build_file)
File ./tools/gyp/pylib/gyp/input.py, line 842, in
ProcessConditionsInDict
if eval(ast_code, {'__builtins__': None}, variables):
File string, line 1, in module
NameError: name 'armv7' is not defined while evaluating condition
'armv7==1'
in /tmp/node-v0.8.0/deps/v8/tools/gyp/v8.gyp while loading dependencies
of
/tmp/node-v0.8.0/node.gyp while trying to load /tmp/node-v0.8.0/node.gyp
Hacking deps/v8/tools/gyp/v8.gyp to just remove the condition that
it's
complaining about at line 997, lets the build continue and complete, but
it
then crashes when built (probably because I'm excluding relevant
switches to
gcc by changing the configure output).
The section of v8.gyp is around line 149:
'conditions': [
['armv7==1', {
Has anyone built node v0.8 or v0.7 on ARM or have some ideas of how to
resolve this?
Gah, I'm still waiting for my BeagleBone.
Does it work when you add `'armv7%':'1'` (sans backticks) to the
variables section of config.gypi or common.gypi?
--
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
Re: [nodejs] Unable to compile node v0.8 RC7 on ARM (Beaglebone)
Also, I've recently noticed that archlinux ARM has nodejs in their
repository. It's usually quite up to date. They support many arm devices
including the beaglebone and the raspberry pi. Even if you don't want to
switch to archlinux or just want a newer node than the one they are
packaging, their PKGBUILD
https://wiki.archlinux.org/index.php/PKGBUILD should
be up somewhere to see how it's done for each platform.
http://archlinuxarm.org/platforms/armv7/beaglebone
http://archlinuxarm.org/packages - search for armv7 and nodejs. Currently
it has v0.6.19
http://archlinuxarm.org/developers/building-packages
On Fri, Jun 22, 2012 at 9:06 AM, Ewan Leith ewan.le...@gmail.com wrote:
Thanks Ben, I added armv7 then it started complaining about arm_neon, so
I've added that too, to deps/v8/build/common.gypi
I've added these 2 lines at the top, just inside the variables section:
'armv7%':'1',
'arm_neon%':'1',
configure completes now, so I'll try a straight make without any
additional compiler flags and see what happens.
Thanks,
Ewan
On Friday, 22 June 2012 14:51:29 UTC+1, Ben Noordhuis wrote:
On Fri, Jun 22, 2012 at 3:39 PM, Ewan Leith wrote:
Hi all, I'm trying to compile node v0.8 rc7 on my beaglebone, and the
configure script it falling over. It does work fine on the 0.6 branch.
Has
anyone built node v0.8 or v0.7 on ARM?
Running configure (with or without -det-cpu=arm) gives the following
output:
./configure --dest-cpu=arm
{ 'target_defaults': { 'cflags': [],
'default_configuration': 'Release',
'defines': [],
'include_dirs': [],
'libraries': []},
'variables': { 'host_arch': 'arm',
'node_install_npm': 'true',
'node_install_waf': 'true',
'node_prefix': '',
'node_shared_openssl': 'false',
'node_shared_v8': 'false',
'node_shared_zlib': 'false',
'node_use_dtrace': 'false',
'node_use_etw': 'false',
'node_use_openssl': 'true',
'strict_aliasing': 'true',
'target_arch': 'arm',
'v8_use_snapshot': 'true'}}
creating ./config.gypi
creating ./config.mk
Traceback (most recent call last):
File tools/gyp_node, line 58, in module
run_gyp(gyp_args)
File tools/gyp_node, line 18, in run_gyp
rc = gyp.main(args)
File ./tools/gyp/pylib/gyp/__init_**_.py, line 471, in main
options.circular_check)
File ./tools/gyp/pylib/gyp/__init_**_.py, line 111, in Load
depth, generator_input_info, check, circular_check)
File ./tools/gyp/pylib/gyp/input.**py, line 2289, in Load
depth, check)
File ./tools/gyp/pylib/gyp/input.**py, line 433, in
LoadTargetBuildFile
includes, depth, check)
File ./tools/gyp/pylib/gyp/input.**py, line 387, in
LoadTargetBuildFile
build_file_path)
File ./tools/gyp/pylib/gyp/input.**py, line 984, in
ProcessVariablesAndConditionsI**nDict
ProcessConditionsInDict(the_**dict, is_late, variables,
build_file)
File ./tools/gyp/pylib/gyp/input.**py, line 861, in
ProcessConditionsInDict
variables, build_file)
File ./tools/gyp/pylib/gyp/input.**py, line 1010, in
ProcessVariablesAndConditionsI**nDict
build_file)
File ./tools/gyp/pylib/gyp/input.**py, line 1025, in
ProcessVariablesAndConditionsI**nList
ProcessVariablesAndConditionsI**nDict(item, is_late, variables,
build_file)
File ./tools/gyp/pylib/gyp/input.**py, line 1010, in
ProcessVariablesAndConditionsI**nDict
build_file)
File ./tools/gyp/pylib/gyp/input.**py, line 1025, in
ProcessVariablesAndConditionsI**nList
ProcessVariablesAndConditionsI**nDict(item, is_late, variables,
build_file)
File ./tools/gyp/pylib/gyp/input.**py, line 984, in
ProcessVariablesAndConditionsI**nDict
ProcessConditionsInDict(the_**dict, is_late, variables,
build_file)
File ./tools/gyp/pylib/gyp/input.**py, line 861, in
ProcessConditionsInDict
variables, build_file)
File ./tools/gyp/pylib/gyp/input.**py, line 984, in
ProcessVariablesAndConditionsI**nDict
ProcessConditionsInDict(the_**dict, is_late, variables,
build_file)
File ./tools/gyp/pylib/gyp/input.**py, line 842, in
ProcessConditionsInDict
if eval(ast_code, {'__builtins__': None}, variables):
File string, line 1, in module
NameError: name 'armv7' is not defined while evaluating condition
'armv7==1'
in /tmp/node-v0.8.0/deps/v8/**tools/gyp/v8.gyp while loading
dependencies of
/tmp/node-v0.8.0/node.gyp while trying to load
/tmp/node-v0.8.0/node.gyp
Hacking deps/v8/tools/gyp/v8.gyp to just remove the condition that
it's
complaining about at line 997, lets the build continue and complete,
but it
then crashes when built (probably because I'm excluding relevant
[nodejs] Re: Sticky sessions using the new cluster API?
There are a couple ways to do this. 1. Use a session store that is transactional and shared (redis etc.) and store where a session should be forwarded to. 2. Use a hashing method that will consistently point to the same location/worker for the same session (session could be ip/user/etc.), if the wrong worker gets the connection, forward it to the original worker. 3. Use a master/slave setup using fork rather than cluster. Master gets all the connections incoming on a machine and processes them before forwarding them to the proper worker. Each method has its advantages. The alternative to this is to change an API to be state-less, which can be hard if connections are using multiple protocols. On Monday, June 18, 2012 11:34:42 PM UTC-5, dhruvbird wrote: Is it possible to have sticky sessions using the new cluster API? Some custom logic such as a cookie based solution? Something similar to nginx sticky module? -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Unable to compile node v0.8 RC7 on ARM (Beaglebone)
The compile completes with those 2 additional lines to
deps/v8/build/common.gypi but running make test raises various errors like
[00:44|% 7|+ 27|- 4]: release test-tls-npn-server-client*** glibc
detected *** out/Release/node: free(): invalid pointer: 0x00717308 ***
so I'll take a look and see if I can work out what's going on.
Thanks,
Ewan
On Friday, 22 June 2012 15:44:59 UTC+1, Tim Caswell wrote:
Also, I've recently noticed that archlinux ARM has nodejs in their
repository. It's usually quite up to date. They support many arm devices
including the beaglebone and the raspberry pi. Even if you don't want to
switch to archlinux or just want a newer node than the one they are
packaging, their PKGBUILD https://wiki.archlinux.org/index.php/PKGBUILD
should
be up somewhere to see how it's done for each platform.
http://archlinuxarm.org/platforms/armv7/beaglebone
http://archlinuxarm.org/packages - search for armv7 and nodejs.
Currently it has v0.6.19
http://archlinuxarm.org/developers/building-packages
On Fri, Jun 22, 2012 at 9:06 AM, Ewan Leith wrote:
Thanks Ben, I added armv7 then it started complaining about arm_neon, so
I've added that too, to deps/v8/build/common.gypi
I've added these 2 lines at the top, just inside the variables section:
'armv7%':'1',
'arm_neon%':'1',
configure completes now, so I'll try a straight make without any
additional compiler flags and see what happens.
Thanks,
Ewan
On Friday, 22 June 2012 14:51:29 UTC+1, Ben Noordhuis wrote:
On Fri, Jun 22, 2012 at 3:39 PM, Ewan Leith wrote:
Hi all, I'm trying to compile node v0.8 rc7 on my beaglebone, and the
configure script it falling over. It does work fine on the 0.6 branch.
Has
anyone built node v0.8 or v0.7 on ARM?
Running configure (with or without -det-cpu=arm) gives the following
output:
./configure --dest-cpu=arm
{ 'target_defaults': { 'cflags': [],
'default_configuration': 'Release',
'defines': [],
'include_dirs': [],
'libraries': []},
'variables': { 'host_arch': 'arm',
'node_install_npm': 'true',
'node_install_waf': 'true',
'node_prefix': '',
'node_shared_openssl': 'false',
'node_shared_v8': 'false',
'node_shared_zlib': 'false',
'node_use_dtrace': 'false',
'node_use_etw': 'false',
'node_use_openssl': 'true',
'strict_aliasing': 'true',
'target_arch': 'arm',
'v8_use_snapshot': 'true'}}
creating ./config.gypi
creating ./config.mk
Traceback (most recent call last):
File tools/gyp_node, line 58, in module
run_gyp(gyp_args)
File tools/gyp_node, line 18, in run_gyp
rc = gyp.main(args)
File ./tools/gyp/pylib/gyp/__init_**_.py, line 471, in main
options.circular_check)
File ./tools/gyp/pylib/gyp/__init_**_.py, line 111, in Load
depth, generator_input_info, check, circular_check)
File ./tools/gyp/pylib/gyp/input.**py, line 2289, in Load
depth, check)
File ./tools/gyp/pylib/gyp/input.**py, line 433, in
LoadTargetBuildFile
includes, depth, check)
File ./tools/gyp/pylib/gyp/input.**py, line 387, in
LoadTargetBuildFile
build_file_path)
File ./tools/gyp/pylib/gyp/input.**py, line 984, in
ProcessVariablesAndConditionsI**nDict
ProcessConditionsInDict(the_**dict, is_late, variables,
build_file)
File ./tools/gyp/pylib/gyp/input.**py, line 861, in
ProcessConditionsInDict
variables, build_file)
File ./tools/gyp/pylib/gyp/input.**py, line 1010, in
ProcessVariablesAndConditionsI**nDict
build_file)
File ./tools/gyp/pylib/gyp/input.**py, line 1025, in
ProcessVariablesAndConditionsI**nList
ProcessVariablesAndConditionsI**nDict(item, is_late, variables,
build_file)
File ./tools/gyp/pylib/gyp/input.**py, line 1010, in
ProcessVariablesAndConditionsI**nDict
build_file)
File ./tools/gyp/pylib/gyp/input.**py, line 1025, in
ProcessVariablesAndConditionsI**nList
ProcessVariablesAndConditionsI**nDict(item, is_late, variables,
build_file)
File ./tools/gyp/pylib/gyp/input.**py, line 984, in
ProcessVariablesAndConditionsI**nDict
ProcessConditionsInDict(the_**dict, is_late, variables,
build_file)
File ./tools/gyp/pylib/gyp/input.**py, line 861, in
ProcessConditionsInDict
variables, build_file)
File ./tools/gyp/pylib/gyp/input.**py, line 984, in
ProcessVariablesAndConditionsI**nDict
ProcessConditionsInDict(the_**dict, is_late, variables,
build_file)
File ./tools/gyp/pylib/gyp/input.**py, line 842, in
ProcessConditionsInDict
if eval(ast_code, {'__builtins__': None}, variables):
[nodejs] process.env.hasOwnProperty
process.env instanceof Object === true typeof process.env.hasOwnProperty === undefined Bug? -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] process.env.hasOwnProperty
On Fri, Jun 22, 2012 at 6:04 PM, Martin Thomson martin.thom...@gmail.com wrote: process.env instanceof Object === true typeof process.env.hasOwnProperty === undefined Bug? `process.env` is not a real JS object. it's a stub for a chunk of C++ code. But by all means file an issue if you feel strongly about this, we can probably fix it. -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] process.env.hasOwnProperty
On Friday, June 22, 2012 6:27:49 PM UTC+2, Ben Noordhuis wrote: `process.env` is not a real JS object. it's a stub for a chunk of C++ code. But by all means file an issue if you feel strongly about this, we can probably fix it. I don't agree. People shouldn't rely on prototype methods of objects that are used as hash tables. Same story for the http headers object, parsed querystring arguments etc. - Bert -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Re: Closures versus Prototypes for Flow Control
On 6/21/12 7:30 AM, Mariusz Nowak wrote: Alan, we use asynchronous programming for tasks that take time, so in that case, whether we wrap such tasks with closure or prototype solution wouldn't make difference in performance. I think debating on performance in that case is pointless. I believe I came to a similar conclusion based on my little experiment, especially since closures offer almost exactly the same performance as a prototype based approach. If it were the case that a prototype based control flow library was an order of magnitude faster than closures, as it appears it would be in Spidermonkey, then it would be worth questioning the costs of closures. -- Alan Gutierrez - http://twitter.com/bigeasy - http://github.com/bigeasy -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Re: Closures versus Prototypes for Flow Control
On Fri, Jun 22, 2012 at 04:21:00AM +1200, Dominic Tarr wrote: also, this is control flow, not flow control. This near collision in nomenclature is most unfortunate, but control flow refers to the transference of control from one phase to the next. (this is the case you are discussing) flow control refers to controling rates of (eg, data) flow through a system. Quite a different concept but also important in node -- when it comes to streaming. I really hate to be this anal, but it's just that I streams are a really great aspect of node and the more people that understand them the better, therefore I want to be as clear as possible. Thank you for correcting me in the nicest way possible. I appreciate the correction. I'm happy to learn the correct the nomenclature. I might even start to sound like I know what I'm talking about. -- Alan Gutierrez - http://twitter.com/bigeasy - http://github.com/bigeasy -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Re: Unable to compile node v0.8 RC7 on ARM (Beaglebone)
Hi,
I'm going to try building node master on my Synology 211j again
(Feroceon 88FR131 rev 1 (v5l))
I remember from past experience that I had to patch SConstruct to pass
-march=armv5t and have armeabi to soft (default was softfp).
It seems now (maybe back then aswell) you I can actually pass --dest-
cpu=armv5t to the configure script (it could be that this also works
for armv7)
Since it takes a long time to compile, I don't know yet if
I'll hit any other roadblocks.
Best regards,
Jeroen
On Jun 22, 3:51 pm, Ben Noordhuis i...@bnoordhuis.nl wrote:
On Fri, Jun 22, 2012 at 3:39 PM, Ewan Leith ewan.le...@gmail.com wrote:
Hi all, I'm trying to compile node v0.8 rc7 on my beaglebone, and the
configure script it falling over. It does work fine on the 0.6 branch. Has
anyone built node v0.8 or v0.7 on ARM?
Running configure (with or without -det-cpu=arm) gives the following output:
./configure --dest-cpu=arm
{ 'target_defaults': { 'cflags': [],
'default_configuration': 'Release',
'defines': [],
'include_dirs': [],
'libraries': []},
'variables': { 'host_arch': 'arm',
'node_install_npm': 'true',
'node_install_waf': 'true',
'node_prefix': '',
'node_shared_openssl': 'false',
'node_shared_v8': 'false',
'node_shared_zlib': 'false',
'node_use_dtrace': 'false',
'node_use_etw': 'false',
'node_use_openssl': 'true',
'strict_aliasing': 'true',
'target_arch': 'arm',
'v8_use_snapshot': 'true'}}
creating ./config.gypi
creating ./config.mk
Traceback (most recent call last):
File tools/gyp_node, line 58, in module
run_gyp(gyp_args)
File tools/gyp_node, line 18, in run_gyp
rc = gyp.main(args)
File ./tools/gyp/pylib/gyp/__init__.py, line 471, in main
options.circular_check)
File ./tools/gyp/pylib/gyp/__init__.py, line 111, in Load
depth, generator_input_info, check, circular_check)
File ./tools/gyp/pylib/gyp/input.py, line 2289, in Load
depth, check)
File ./tools/gyp/pylib/gyp/input.py, line 433, in LoadTargetBuildFile
includes, depth, check)
File ./tools/gyp/pylib/gyp/input.py, line 387, in LoadTargetBuildFile
build_file_path)
File ./tools/gyp/pylib/gyp/input.py, line 984, in
ProcessVariablesAndConditionsInDict
ProcessConditionsInDict(the_dict, is_late, variables, build_file)
File ./tools/gyp/pylib/gyp/input.py, line 861, in
ProcessConditionsInDict
variables, build_file)
File ./tools/gyp/pylib/gyp/input.py, line 1010, in
ProcessVariablesAndConditionsInDict
build_file)
File ./tools/gyp/pylib/gyp/input.py, line 1025, in
ProcessVariablesAndConditionsInList
ProcessVariablesAndConditionsInDict(item, is_late, variables,
build_file)
File ./tools/gyp/pylib/gyp/input.py, line 1010, in
ProcessVariablesAndConditionsInDict
build_file)
File ./tools/gyp/pylib/gyp/input.py, line 1025, in
ProcessVariablesAndConditionsInList
ProcessVariablesAndConditionsInDict(item, is_late, variables,
build_file)
File ./tools/gyp/pylib/gyp/input.py, line 984, in
ProcessVariablesAndConditionsInDict
ProcessConditionsInDict(the_dict, is_late, variables, build_file)
File ./tools/gyp/pylib/gyp/input.py, line 861, in
ProcessConditionsInDict
variables, build_file)
File ./tools/gyp/pylib/gyp/input.py, line 984, in
ProcessVariablesAndConditionsInDict
ProcessConditionsInDict(the_dict, is_late, variables, build_file)
File ./tools/gyp/pylib/gyp/input.py, line 842, in
ProcessConditionsInDict
if eval(ast_code, {'__builtins__': None}, variables):
File string, line 1, in module
NameError: name 'armv7' is not defined while evaluating condition 'armv7==1'
in /tmp/node-v0.8.0/deps/v8/tools/gyp/v8.gyp while loading dependencies of
/tmp/node-v0.8.0/node.gyp while trying to load /tmp/node-v0.8.0/node.gyp
Hacking deps/v8/tools/gyp/v8.gyp to just remove the condition that it's
complaining about at line 997, lets the build continue and complete, but it
then crashes when built (probably because I'm excluding relevant switches to
gcc by changing the configure output).
The section of v8.gyp is around line 149:
'conditions': [
['armv7==1', {
Has anyone built node v0.8 or v0.7 on ARM or have some ideas of how to
resolve this?
Gah, I'm still waiting for my BeagleBone.
Does it work when you add `'armv7%':'1'` (sans backticks) to the
variables section of config.gypi or common.gypi?
--
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
[nodejs] Mongoosastic 0.0.5 Released
Hey All, Just wanted to announce that 0.0.5 of mongoosastic ( http://jamescarr.github.com/mongoosastic/) has been released. This release adds the ability to add per field options to mongoose models that get applied to the mapping in elasticsearch (such as boost, null_value, etc). As always pull requests and open issues are always welcomed! Thanks, James -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Node and developing on multiple machines
Hi, It's very common that I use several machines while developing and those machines might also be in different locations. I have two machines at home and two machines at my moms etc. There might be more machines in the future. My problem is this. No matter where I am, I just want to sit down and code and not care about what modules I have installed and where. If I'm visiting my mom some day I might find this uber cool module and install it globally with npm on that machine. When I get back home I'd like to sync my global modules on my other machines, instead of having to remember that I installed module X on machine Y. Do you have any recommendations? Thanks /Magnus -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Node and developing on multiple machines
dropbox On Fri, Jun 22, 2012 at 2:52 PM, Ralphtheninja (Magnus Skog) lars.magnus.s...@gmail.com wrote: Hi, It's very common that I use several machines while developing and those machines might also be in different locations. I have two machines at home and two machines at my moms etc. There might be more machines in the future. My problem is this. No matter where I am, I just want to sit down and code and not care about what modules I have installed and where. If I'm visiting my mom some day I might find this uber cool module and install it globally with npm on that machine. When I get back home I'd like to sync my global modules on my other machines, instead of having to remember that I installed module X on machine Y. Do you have any recommendations? Thanks /Magnus -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Node and developing on multiple machines
That wont work for binary modules. Is it such an overkill to just install global modules on the fly as you need them? on any computer. On 06/23/2012 01:00 AM, Elijah Insua wrote: dropbox On Fri, Jun 22, 2012 at 2:52 PM, Ralphtheninja (Magnus Skog) lars.magnus.s...@gmail.com mailto:lars.magnus.s...@gmail.com wrote: Hi, It's very common that I use several machines while developing and those machines might also be in different locations. I have two machines at home and two machines at my moms etc. There might be more machines in the future. My problem is this. No matter where I am, I just want to sit down and code and not care about what modules I have installed and where. If I'm visiting my mom some day I might find this uber cool module and install it globally with npm on that machine. When I get back home I'd like to sync my global modules on my other machines, instead of having to remember that I installed module X on machine Y. Do you have any recommendations? Thanks /Magnus -- 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 nodejs@googlegroups.com mailto:nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com mailto:nodejs%2bunsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Node and developing on multiple machines
For what it's worth, I have my only development environment on one server and I just remote into it from all the others. I literally see the same exact environment everywhere. On Fri, Jun 22, 2012 at 3:00 PM, Elijah Insua tmp...@gmail.com wrote: dropbox On Fri, Jun 22, 2012 at 2:52 PM, Ralphtheninja (Magnus Skog) lars.magnus.s...@gmail.com wrote: Hi, It's very common that I use several machines while developing and those machines might also be in different locations. I have two machines at home and two machines at my moms etc. There might be more machines in the future. My problem is this. No matter where I am, I just want to sit down and code and not care about what modules I have installed and where. If I'm visiting my mom some day I might find this uber cool module and install it globally with npm on that machine. When I get back home I'd like to sync my global modules on my other machines, instead of having to remember that I installed module X on machine Y. Do you have any recommendations? Thanks /Magnus -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Re: forever and cpu usage
El viernes, 22 de junio de 2012 08:54:17 UTC-4, Angelo Chen escribió: Hi, I run my node with forever, it works quite well, got two questions: 1) at any given time, there are two node running, that's normal? forever run in one instance of node.js your app runs in another. -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Should i use node?
I have a medium size application in Rails that is consuming lot of resources because it has to communicate with a SOAP web service, every time the application accesses the service is the processing of the request stops so i have to have start many instances to make the app respond quickly to the other clients, i also have to start faye and several background workers. So is it a better idea to port this application to node.js (expressjs) and make async calls to the SOAP web service and update the clients via socket.io? What kind of issues should i be aware of? -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Node and developing on multiple machines
I do the same as Mark, a few cloud servers that I remote into for development. I'm often jumping between a mix of several Win7/Centos/Ubuntu machines - to do remote development I use the following scenarios: 1. On either, ssh with console vim. 2. On linux, I'll do a fuse ssh filesystem mount and then use vim/sublime text. 3. On windows, I do an ssh tunnel samba mount to local drive, then vim/sublime text. Whatever I'm working on is either tunneled to a local port to access via browser, or behind http auth. On Fri, Jun 22, 2012 at 3:07 PM, Mark Hahn m...@hahnca.com wrote: For what it's worth, I have my only development environment on one server and I just remote into it from all the others. I literally see the same exact environment everywhere. On Fri, Jun 22, 2012 at 3:00 PM, Elijah Insua tmp...@gmail.com wrote: dropbox On Fri, Jun 22, 2012 at 2:52 PM, Ralphtheninja (Magnus Skog) lars.magnus.s...@gmail.com wrote: Hi, It's very common that I use several machines while developing and those machines might also be in different locations. I have two machines at home and two machines at my moms etc. There might be more machines in the future. My problem is this. No matter where I am, I just want to sit down and code and not care about what modules I have installed and where. If I'm visiting my mom some day I might find this uber cool module and install it globally with npm on that machine. When I get back home I'd like to sync my global modules on my other machines, instead of having to remember that I installed module X on machine Y. Do you have any recommendations? Thanks /Magnus -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- John R. Fitzgerald -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] process.env.hasOwnProperty
On Fri, Jun 22, 2012 at 7:22 PM, Bert Belder bertbel...@gmail.com wrote: On Friday, June 22, 2012 6:27:49 PM UTC+2, Ben Noordhuis wrote: `process.env` is not a real JS object. it's a stub for a chunk of C++ code. But by all means file an issue if you feel strongly about this, we can probably fix it. I don't agree. People shouldn't rely on prototype methods of objects that are used as hash tables. Same story for the http headers object, parsed querystring arguments etc. Apparently Bert feels strongly about this. :-) -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Should i use node?
Node sounds like a fit to me. Why do you have workers? Doesn't rails automatically use threads/processes to allow multiple things to happen at once? (I know nothing about how a rails server works). On Fri, Jun 22, 2012 at 12:32 PM, Radhames Brito rbri...@techpark.com.dowrote: I have a medium size application in Rails that is consuming lot of resources because it has to communicate with a SOAP web service, every time the application accesses the service is the processing of the request stops so i have to have start many instances to make the app respond quickly to the other clients, i also have to start faye and several background workers. So is it a better idea to port this application to node.js (expressjs) and make async calls to the SOAP web service and update the clients via socket.io? What kind of issues should i be aware of? -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] NODE_PATH deprecated?
On Tue, Jun 19, 2012 at 1:06 PM, Oliver Leics oliver.le...@gmail.com wrote: The PLUS is now a MINUS as it came out that it is _not_ the missing NODE_PATH env var that makes the installation of dtrace-provider fail on a LinuxDebian box. No, my guess is that it's the lack of DTrace on Linux that makes it fail. OT @Isaac: Please see https://github.com/mcavage/node-restify/issues/161 That's a general feature request for npm (i.e., install X without Y). Probably not going to happen. I could see a use for a Never even try to install package xyz type of option in npm, but it should be a feature request, and would need some discussion to flesh out exactly how it works. In most cases (including, in my opinion, this one) an optionalDependency is exactly the right fit. -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] process.env.hasOwnProperty
process.env should be a real js object, or at least act like one. if we have to i'd say we make process.env a getter and build a real js object from the C++ stub that is currently there. people should not be expected to know or distinguish between normal js objects and crazy things from C++. -Mikeal On Jun 22, 2012, at June 22, 20124:58 PM, Ben Noordhuis wrote: On Fri, Jun 22, 2012 at 7:22 PM, Bert Belder bertbel...@gmail.com wrote: On Friday, June 22, 2012 6:27:49 PM UTC+2, Ben Noordhuis wrote: `process.env` is not a real JS object. it's a stub for a chunk of C++ code. But by all means file an issue if you feel strongly about this, we can probably fix it. I don't agree. People shouldn't rely on prototype methods of objects that are used as hash tables. Same story for the http headers object, parsed querystring arguments etc. Apparently Bert feels strongly about this. :-) -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] NODE_PATH deprecated?
On Sat, Jun 23, 2012 at 2:00 AM, Isaac Schlueter i...@izs.me wrote: On Tue, Jun 19, 2012 at 1:06 PM, Oliver Leics oliver.le...@gmail.com wrote: The PLUS is now a MINUS as it came out that it is _not_ the missing NODE_PATH env var that makes the installation of dtrace-provider fail on a LinuxDebian box. No, my guess is that it's the lack of DTrace on Linux that makes it fail. Yes, it fails because of this. Nevertheless restify should install. But the good news is: Problem solved for me, see https://github.com/isaacs/npm/issues/2546 OT @Isaac: Please see https://github.com/mcavage/node-restify/issues/161 That's a general feature request for npm (i.e., install X without Y). Probably not going to happen. I could see a use for a Never even try to install package xyz type of option in npm, but it should be a feature request, and would need some discussion to flesh out exactly how it works. I don't like to fill blacklists. In most cases (including, in my opinion, this one) an optionalDependency is exactly the right fit. I see it the same way for dependencies that are okay to fail on install. But, for example, I saw your commit to tako that makes socket.io optional by a try-catch. How to state in package.json that socket.io can be used but must be installed by hand? -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] forever and cpu usage
On Fri, Jun 22, 2012 at 2:54 PM, Angelo Chen angelochen...@gmail.com wrote: 1) at any given time, there are two node running, that's normal? forever spawns a new process and that is your node monitored by forever. So, yes, this is absolutely normal. On the other hand, _only_ two nodes-processes is absolutely not normal ;-) -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Node 0.1.1 to 0.8.0
So i was just looking at the source of node https://github.com/joyent/node/tree/v0.1.1 and I'm just amazed at how far it has come in the past few years. The days of res.sendBody and res.finish are far memory to some and unknown to others. I don't know where i would be with out node. I love it and its amazing! Thanks very must to ry! Just my 2cents. Thanks -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Re: Node and developing on multiple machines
Look at cloud9, its all web based. On Friday, June 22, 2012 5:52:25 PM UTC-4, Ralphtheninja (Magnus Skog) wrote: Hi, It's very common that I use several machines while developing and those machines might also be in different locations. I have two machines at home and two machines at my moms etc. There might be more machines in the future. My problem is this. No matter where I am, I just want to sit down and code and not care about what modules I have installed and where. If I'm visiting my mom some day I might find this uber cool module and install it globally with npm on that machine. When I get back home I'd like to sync my global modules on my other machines, instead of having to remember that I installed module X on machine Y. Do you have any recommendations? Thanks /Magnus -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Re: Should i use node?
On 22 jun, 19:58, Mark Hahn m...@hahnca.com wrote: Node sounds like a fit to me. Why do you have workers? Doesn't rails automatically use threads/processes to allow multiple things to happen at once? (I know nothing about how a rails server works). On the contrary, Ryan used rails as an example of way node should exists, rails is single threaded. The why to rails can only answer one request at a time. The way rails is scaled is by starting/forking more servers, if your app uses 40MB in memory, and you can answer a request every 200ms you can handle 5 clients per second, so if you want responses you need more rails servers running(forked) 30 instances will answer to 150 concurrent request per second but will use 1.2 GB of ram. Also scaling with rails involve caching parts of the serve html so the app gets out of the way and lets the native servers (apache which is threaded or ngingx which is evented) handle serving the cached asset or peace of html. Any interaction with anything that can block (talking to an external service) will block that instance for all clients so if a client if sending several emails in one request, other clients cant be served by rails until the process ends. That is way background processes are used, you put the data in a queue(redis for example) for inter process communication and you have another instance of rails which usually doesnt do anything but process the background jobs pick up the data and do the jobs, that instance if usually performing a time based loop waiting for anything to appear in the queue. So trying to integrate rails with for example, an external web service or evented telephony is a REAL PAIN. -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Re: Should i use node?
On 22 jun, 20:04, Ben Noordhuis i...@bnoordhuis.nl wrote: On Fri, Jun 22, 2012 at 9:32 PM, Radhames Brito rbri...@techpark.com.do wrote: I have a medium size application in Rails that is consuming lot of resources because it has to communicate with a SOAP web service, every time the application accesses the service is the processing of the request stops so i have to have start many instances to make the app respond quickly to the other clients, i also have to start faye and several background workers. So is it a better idea to port this application to node.js (expressjs) and make async calls to the SOAP web service and update the clients via socket.io? That's exactly the use case node.js was designed for: shoveling loads of data from one network endpoint to another. What kind of issues should i be aware of? That event-driven I/O is something of a paradigm shift. It takes some getting used to but if you've used e.g. EventMachine before, you'll be fine. The biggest problem for me is that there seems to be no standard for anything and the community is segregated. Many projects are redundant and when one has a feature you need is missing something else that another project has but is missing some other feature. Most project lack the proper documentation. I dont see node.js growing much as long as there is no central leadership of some sort that can impose some standars like, everything in npm must be documented this way or this other, or if you are doing the same thing as someone else dont duplicate efforts join that project and help build one robust solution. There are like 5 ORM (most lack support for relational databases) , 3 SOAP clients (none fully featured), 10 RoR clones (all missing one thing that the other has), 8 mailers and so on. So many smart people doing great things but most are not what the could because everyone seems to want to be the next DHH or something. I mean if towerjs, railwayjs and geddy are all trying to copy RoR why not just get together and do one excellent solution? Sorry for the rant. -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] process.env.hasOwnProperty
Object.create(null) ? :-) On Friday, June 22, 2012 8:02:47 PM UTC-4, Isaac Schlueter wrote: I somewhat agree with Bert here. On the other hand, we just outright block querystrings from having keys named hasOwnProperty, __defineGetter__, etc., and I believe we may do the same for http headers. We probably ought to make a decision and have them all work the same. I'd be tempted to maybe add some kind of not instanceof Object object goober and use for these cases. On Fri, Jun 22, 2012 at 4:58 PM, Ben Noordhuis wrote: On Fri, Jun 22, 2012 at 7:22 PM, Bert Belder wrote: On Friday, June 22, 2012 6:27:49 PM UTC+2, Ben Noordhuis wrote: `process.env` is not a real JS object. it's a stub for a chunk of C++ code. But by all means file an issue if you feel strongly about this, we can probably fix it. I don't agree. People shouldn't rely on prototype methods of objects that are used as hash tables. Same story for the http headers object, parsed querystring arguments etc. Apparently Bert feels strongly about this. :-) -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Re: Should i use node?
Well, node.js is a bit like the Wild West, before the railroads where built, and in my book this is a very good thing. Projects get traction or they don't, based on what people like or dislike. No big hand watching over us forcing us into doing it in a certain way. Or, more like Shadows and less like Vorlons. And in the long run this will become the strongest platform because of this. On Fri, Jun 22, 2012 at 9:11 PM, Radhames Brito rbri...@techpark.com.dowrote: On 22 jun, 20:04, Ben Noordhuis i...@bnoordhuis.nl wrote: On Fri, Jun 22, 2012 at 9:32 PM, Radhames Brito rbri...@techpark.com.do wrote: I have a medium size application in Rails that is consuming lot of resources because it has to communicate with a SOAP web service, every time the application accesses the service is the processing of the request stops so i have to have start many instances to make the app respond quickly to the other clients, i also have to start faye and several background workers. So is it a better idea to port this application to node.js (expressjs) and make async calls to the SOAP web service and update the clients via socket.io? That's exactly the use case node.js was designed for: shoveling loads of data from one network endpoint to another. What kind of issues should i be aware of? That event-driven I/O is something of a paradigm shift. It takes some getting used to but if you've used e.g. EventMachine before, you'll be fine. The biggest problem for me is that there seems to be no standard for anything and the community is segregated. Many projects are redundant and when one has a feature you need is missing something else that another project has but is missing some other feature. Most project lack the proper documentation. I dont see node.js growing much as long as there is no central leadership of some sort that can impose some standars like, everything in npm must be documented this way or this other, or if you are doing the same thing as someone else dont duplicate efforts join that project and help build one robust solution. There are like 5 ORM (most lack support for relational databases) , 3 SOAP clients (none fully featured), 10 RoR clones (all missing one thing that the other has), 8 mailers and so on. So many smart people doing great things but most are not what the could because everyone seems to want to be the next DHH or something. I mean if towerjs, railwayjs and geddy are all trying to copy RoR why not just get together and do one excellent solution? Sorry for the rant. -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
