On Wednesday, September 19, 2012 1:50:32 AM UTC+2, Isaac Schlueter wrote:
Bruno, I think your comments belong in the other discussion. This is
what I was referring to in that lame shared-state data corruption pun
I made earlier, about sharing data across threads :)
On Tue, Sep 18, 2012
Thanks Ban and Nathan
Actually i tried both the methods and get the error
*NameError: name 'arm_neon' is not defined while evaluating condition
'arm_neon!=1 and arm_fpu!=vfpv3 and arm_fpu!=vfpv3-d16' in
/home/nodejs/deps/v8/tools/gyp/v8.gyp while loading dependencies of
/home/nodejs/node.gyp
Commented following portion in deps/v8/tools/gyp/v8.gyp and compilation
was success with --without-snapshot option
149 'conditions': [
150 ['armv7==1', {
151 # The ARM Architecture Manual mandates VFPv3
if NEON is
152
Able to run Test program on my embedded board. still i am thinking about
1. compiling with --without-snapshot option. and how does it will effect
the performance.
2. and modfication did in deps/v8/tools/gyp/v8.gyp
can someone please explain the impact of these on my system's performance.
On Wed, Sep 19, 2012 at 10:41 AM, Sumit Aggarwal getsumit...@gmail.com wrote:
Commented following portion in deps/v8/tools/gyp/v8.gyp and compilation was
success with --without-snapshot option
149 'conditions': [
150 ['armv7==1', {
151
Hi Ben,
Patch did work for me. Thanks for the help
--
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
On Wed, Sep 19, 2012 at 2:27 PM, Sumit Aggarwal getsumit...@gmail.com wrote:
Hi Ben,
Patch did work for me. Thanks for the help
Thanks for testing. Landed in master.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
Wow, that is an awesome tip.
I really want see my nodes running in tablates or phones.
Em quarta-feira, 19 de setembro de 2012 09h27min38s UTC-3, Sumit Aggarwal
escreveu:
Hi Ben,
Patch did work for me. Thanks for the help
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
0.8.9 on linux build from source.
Am Dienstag, 18. September 2012 13:53:51 UTC+2 schrieb Fedor Indutny:
And btw, what node.js version are you using?
On Tue, Sep 18, 2012 at 3:37 PM, Ben Noordhuis
in...@bnoordhuis.nljavascript:
wrote:
On Tue, Sep 18, 2012 at 1:27 PM, Michael
Mariusz,
memoize looks really nice! I am going to try it out for some projects I am
working on.
As for suggestions:
- you might consider wrapping the file in a function closure so it can be
used directly in a browser
- could you add a LRU option? (I know you have many other algorithms, but
Mariusz,
I took a closer look and realized that there a many dependencies (I was
thinking it was self contained), so not as simple to get into the browser,
either need to use something like AMD or build a distribution file with one
of the commonsjs browser build solutions.
Jeff
On
Hello,
I am trying to create a repl, that will mostly call async ops.
How can i pause it until the async operation is over?
Something like the mongo repl.
Thanks,
danmilon.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
Jeff,
It can easily be ported to browser with help of
Webmake https://github.com/medikoo/modules-webmake (it's mentioned in
documentation)
Anyway to make it even easier I prepared a bundle -
https://github.com/medikoo/memoize/downloads ;)
According to LRU option, you can achieve it with 'max'
I just came up against this trying to proxy a stream. This seems to work
for me:
proxy.on 'pipe', (pipeSrc) -
src = pipeSrc
proxy.pipe = (pipeDest) -
unless proxied
throw new Error 'proxied stream has not been enabled'
src.removeAllListeners()
Mariusz,
You are right, I missed the mention in the readme about building it for the
browser, but it is nice that you prepared a download bundle. Honestly I
just went right to the code first and only glanced at the README for the
API, so I ended up missing that.
Correct me if I am wrong, but
All,
Is there a way to stop node from terminating when data is piped to it? I
tried with -i with no luck.
i.e. the following prints out the input data then stops, whereas I expect
my readline to kick in:
echo | node test.js
```
// test.js
var readline = require('readline'),
rl =
Tomorrow!
Thursday, 20 September 2012, 6:30pm
Saint Louis, Missouri, USA
STLJS Meetup in the The Able Few's corporate offices:
Nick Apperson will present Scaling Node.js to tens of thousands of
concurrent users and beyond
http://www.stljs.org/events/68051712/
Don't forget to RSVP!
I wasn't really addressing you—your comments were entirely reasonable. I
was addressing the shit-talking dog-pile.
I challenge you to find anything in this thread that directly shit-talks
Node or Joyent. I *want* to believe this is fair and balanced discussion.
Jorge got a little tweaked
Yes they do. I'm following this through the Google web UI. The two
discussions are interleaved in a single list and I did not pay attention to
the titles. Maybe Google does not like threads either :-)
Sorry! I see the same WTF'itude: I meant to cleanly fork provide some
consistency,
On Wed, Sep 19, 2012 at 5:23 PM, rektide rekt...@voodoowarez.com wrote:
I wasn't really addressing you—your comments were entirely reasonable. I
was addressing the shit-talking dog-pile.
I challenge you to find anything in this thread that directly shit-talks
Node or Joyent. I *want* to
Dan,
What are your goals in pausing the REPL? Especially when working with the
REPL on a running application, I find invoking async operations with a
callback like this one https://npmjs.org/package/repl-callback to be a
lot more useful. Not saying you have to use that module or that your
See https://gist.github.com/3751746 for details.
Basically, in Node 0.6, if you start a child_process with
child_process.spawn, the pipe2 system call was used to create the
pipes between parent and child.
This was changed (I believe) in this commit by indutny:
On Wed, Sep 19, 2012 at 9:54 PM, David Glasser glas...@meteor.com wrote:
See https://gist.github.com/3751746 for details.
Basically, in Node 0.6, if you start a child_process with
child_process.spawn, the pipe2 system call was used to create the
pipes between parent and child.
This was
On Sep 19, 2012, at September 19, 20123:21 PM, rektide
rekt...@voodoowarez.com wrote:
I humbly propose not participating in things which annoy you or you find
overly distracting.
Mikeal was complaining about nothing except people discussing things, about
feeling hurt for others
Ah, yes, that'll do it. And yes, that's the workaround we're using.
--
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
On Wednesday, September 19, 2012 6:30:07 PM UTC-4, Mikeal Rogers wrote:
On Sep 19, 2012, at September 19, 20123:21 PM, rektide
rek...@voodoowarez.com javascript: wrote:
I humbly propose not participating in things which annoy you or you
find overly distracting.
Mikeal was
This whole thread business [pun intended] is about the deadest horse
ever to have lived...
I will say this, out of all the mailing lists I am on... This is the
only one that gets these huge conversations where the majority of the
content is pointless to actually improving the community... (and
This issue is done.
No, Isaac. I feel pissed on here. Ack that.
Ack'ed.
Your original request for threads-in-node has been met with
explanations from me, Ben, and Paddybyers about what would need to be
done to make that happen, and what the challenges are. There's
nothing else to discuss
I've noticed that quite a lot of Node.js packages are tagging version
number zero for all their releases: 0.4.0, 0.9.9, 0.0.1, 0.27.4, etc (to
pick from packages that I use). It's as if people think that if the program
is not fully feature-complete, they shouldn't release version 1.0.0.
You
I gently suggest that if we'd found and settled on some technical topics,
rather than meta-moderation, there would be six or seven posts here. If you
feel topics not to your interest, I revert to my former stance which is:
don't read them.
This is a mailing list: 8/10 topics have no interest
On Wednesday, September 19, 2012 8:55:00 PM UTC-4, Isaac Schlueter wrote:
No, Isaac. I feel pissed on here. Ack that.
Ack'ed.
Your original request for threads-in-node has been met with
explanations from me, Ben, and Paddybyers about what would need to be
done to make that happen,
ps. I'm really a nice guy, hopefully we can meet in person some day and
we'll laugh about this.
Me too. I interpretted some subset of the conversation here as your
intended target of shit-talking dogpile people, which didn't seem fair to
me. Since you've disavowed that connection,
I am trying to create a http caching proxy server using node.js , where i
could forward to any webpages and cached them on my local disk !
The following is my first attempt code :
var http = require('http'),
url = require('url'),
sys = require('url');
var fs = require('fs');
var port =
Hello Ben and Moreira
i want to use nodejs for enhancement of device capabilities and want to do
something like this
1. Make device as http web server. something like done by nokia
http://research.nokia.com/page/231;.
So that i can expose device capabilities to a web application and making
34 matches
Mail list logo
