Hi Liam,
Jorge is working on it and I'm trying to help with the little time I have.
It should show up on GitHub soon. Stay tuned.
Bruno
On Thursday, March 1, 2012 9:41:15 PM UTC+1, Liam wrote:
Hey Jorge Bruno, any progress? Maybe you should just post what
you've got to github...
On Feb
Hi Gurus,
I'm trying to convert some related large XML files (~30MB) to JSON format.
I've tried some out of box solutions such as xml2js, xml2json. All of them
consumes a lot of memory (200~300MB) ,so I'm wondering if there are modules
that are less memory hungry.
After the JSON string is
Have a look at https://github.com/isaacs/sax-js
On Friday, March 2, 2012 3:46:35 AM UTC-7, Felix Wan wrote:
Hi Gurus,
I'm trying to convert some related large XML files (~30MB) to JSON format.
I've tried some out of box solutions such as xml2js, xml2json. All of them
consumes a lot of
On Fri, Mar 2, 2012 at 7:04 PM, fent roly...@gmail.com wrote:
Have a look at https://github.com/isaacs/sax-js
xml2js is built on top of sax-js. I even hacked version to utilize the
streaming API provided by sax-js, but doesn't help too much.
--
: ~
--
Job Board: http://jobs.nodejs.org/
No, saxjs cant be using all that memory. xml2js is probably doing some
buffering of its own that justifies that memory usage.
I've seen the saxjs code and the buffers are very well kept, plus you
can set a limit after which buffers will be purged.
Nuno
On Fri, Mar 2, 2012 at 11:07 AM, Wan Li
On Fri, Mar 2, 2012 at 10:45, Erik Dubbelboer e...@dubbelboer.com wrote:
Calling eio_set_min_parallel() from a module still seems to work (only on
unix I guess). What exactly has moved to libuv?
All the platform-specific code. eio_set_min_parallel() still works
because libuv is compiled without
Hello,
I recently updated Node to version 0.6.11 and I have now problems when
trying to use node-waf to compile a native addon.
Here is the error I have:
Traceback (most recent call last):
File /usr/local/bin/node-waf, line 16, in module
Scripting.prepare(t, os.getcwd(), VERSION,
On Thursday, March 1, 2012 11:50:21 PM UTC+1, Ben Noordhuis wrote:
On Thu, Mar 1, 2012 at 22:16, Erik Dubbelboer e...@dubbelboer.com wrote:
Hi Everyone,
I was wondering what the status is for this API. I couldn't find
anything in
the current documentation so I'm guessing it hasn't been
On Fri, Mar 2, 2012 at 14:14, Erik Dubbelboer e...@dubbelboer.com wrote:
On Thursday, March 1, 2012 11:50:21 PM UTC+1, Ben Noordhuis wrote:
On Thu, Mar 1, 2012 at 22:16, Erik Dubbelboer e...@dubbelboer.com wrote:
Hi Everyone,
I was wondering what the status is for this API. I couldn't
I can't help you with your problem but I will say that maybe you should be
moving to node-gyp since it is the replacement for node-waf? At least
according to TTN it is :)
https://github.com/TooTallNate/node-gyp
node-gyp is a cross-platform command-line tool written in Node.js for
compiling
I'm looking for suggestions on detecting when the NodeJS event loop is
blocked (due to CPU-intensive code), and determining what is causing the
block.
I'm running a rather large NodeJS app. Over time, as the app and dataset
have grown, things that used to process quickly have become more
*add HTTP proxy support (I should check more before sending)
On Fri, Mar 2, 2012 at 8:29 AM, Tim Caswell t...@creationix.com wrote:
I don't have experience with hiding source code (I tend to put everything
I write on github out of habit), but I do know about keeping parts of code
secure and
It will need some adjusting, but the event source hooks I wrote for
[trycatch] allow you to insert code at the root of an event stack. You can
create a timestamp before the first function is called, and another when it
returns. if the difference is larger that some preset, you can flag that
Hi,
Any recommendations for the following would be much appreciated:
1. Monitor the 'health' of the NodeJS event loop, to know 'how big the
problem is' – any extended blocking of the event loop is a Bad Thing, so
seems a Good Practice to detect when blocking happens.
As a very simple
Did not have a look yet at how works libuv and eio, I'm more from the
JavaScript side, it's years I haven't look seriously at some C/C++.
Any help to do it as a module, any track to start, is very welcome :)
Cheers,
Florian
2012/3/1 Brandon Philips brandon.phil...@rackspace.com
Hey Florian-
One simple approach is to simply try to slow down the competition from
stealing your code. Minimizing your code with something like uglify, should
make it harder for someone to take code and continue to work with it (to
make enhancements and changes), at least it would slow them down.
Then
On Mar 2, 2012, at 2:14 PM, Erik Dubbelboer wrote:
On Thursday, March 1, 2012 11:50:21 PM UTC+1, Ben Noordhuis wrote:
On Thu, Mar 1, 2012 at 22:16, Erik Dubbelboer e...@dubbelboer.com wrote:
Hi Everyone,
I was wondering what the status is for this API. I couldn't find anything in
the
On Friday, March 2, 2012 5:11:04 PM UTC+1, Jorge wrote:
Please note that time passes in parallel (N threads doing usleep()s in
parallel are always going to be faster than MN threads running N
usleep()s), but real disk I/O jobs even when ran in parallel in separate
threads tend to be
On Mar 2, 5:47 am, Ben Noordhuis i...@bnoordhuis.nl wrote:
Maybe I should've mentioned that I'm mostly interested in file I/O,
that still being something of a weak spot in Node. :-)
Well one common file i/o op would be improved by enabling sendfile()
to a socket :-)
Also, there was this
It's amazing. I've never seen anything get such a good response. The
stripe people must read this with a big grin.
--
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
But having a lot of different events, like many users pulling pages at
once, would give a bad result in that test. Not that is doesn't sound
useful in general.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You
hope they're coming to the uk soon
--
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
On Mar 2, 3:28 pm, Jimb Esser wastel...@gmail.com wrote:
The child_process module launches the children with piped stdout and
stdin, and most processes will exit when they try to write to or read
from a broken pipe (is your spawned app printing something to
stdout?). I don't know of any
2012.03.02 Version 0.6.12 (stable)
* Upgrade V8 to 3.6.6.24
* dtrace ustack helper improvements (Dave Pacheco)
* API Documentation refactor (isaacs)
* #2827 net: fix race write() before and after connect() (koichik)
* #2554 #2567 throw if fs args for 'start' or 'end' are strings (AJ ONeal)
*
hoorah!
Only because I'm currently looking at it... when's ETA for dgram functions
like setTTL et. al. ?
dave
On Friday, 2 March 2012 21:22:14 UTC, Isaac Schlueter wrote:
2012.03.02 Version 0.6.12 (stable)
* Upgrade V8 to 3.6.6.24
* dtrace ustack helper improvements (Dave Pacheco)
*
On Fri, Mar 2, 2012 at 23:37, Dave Clements huperekch...@googlemail.com wrote:
hoorah!
Only because I'm currently looking at it... when's ETA for dgram functions
like setTTL et. al. ?
dave
Dave, they've been back since v0.6.9.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
i posted a gist on github with an example, using Joe Ferners node-java
to interface to the AntiSamy java library for HTML sanitization
https://gist.github.com/1961957
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
For various reasons, we've got our node.js server running behind a
protocol-agnostic (dumb TCP-pass through) reverse proxy/load balancer
and SSL terminators, and we need to get the IP address of the original
connection. HTTP header rewriting isn't feasible because of the
protocol-agnostic load
On Fri, Mar 2, 2012 at 23:46, Jimb Esser wastel...@gmail.com wrote:
For various reasons, we've got our node.js server running behind a
protocol-agnostic (dumb TCP-pass through) reverse proxy/load balancer
and SSL terminators, and we need to get the IP address of the original
connection. HTTP
Haha, glad somebody appreciated it :)
On Fri, Mar 2, 2012 at 3:08 PM, Shinuza samorigo...@gmail.com wrote:
Sweet addition to the REPL
https://gist.github.com/1962163
On Friday, March 2, 2012 10:22:14 PM UTC+1, Isaac Schlueter wrote:
2012.03.02 Version 0.6.12 (stable)
* Upgrade V8 to
On Mar 2, 5:45 pm, dmh2000 dmh2...@gmail.com wrote:
i posted a gist on github with an example, using Joe Ferners node-java
to interface to the AntiSamy java library for HTML
sanitizationhttps://gist.github.com/1961957
Why not use something with less overhead, like one of the sanitization
We have a load balancer running in front of our node.js servers, so by
the time the connection gets to our node.js server, the socket's
remote address is always the IP of our load balancer. We want to get
the original IP of the original connection, and most load balancers
and SSL terminators
My lib is not in production. I was more of an effort to explore TDS and I
do plan on maintaining it. My day job is keeping me from doing too much
right now though. I believe Mike's repository is more active and may be a
better solution.
On Thursday, March 1, 2012 6:02:56 PM UTC-6, Neville
Well, technically Stripe IS a payment gateway, so when they say you
don't need one they just mean you don't need another one besides them
(or whoever they partnered with).
It's nice that they have a fancy AJAXy payment submission process,
though, and that they publish their rate (it's higher than
Which is the point of the whole exercise. You do not need a merchant
account. You do not need a separate payment gateway. Stripe takes care of
that.
Given the amount of pain and suffering and time it takes to deal with
merchant accounts, the hidden fees, and paypals mission to make customer
Perhaps something like https://github.com/mape/node-profile would 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
36 matches
Mail list logo
