On May 18, 2012, at 7:10 AM, Aleksander Adamowski wrote:
> On Wednesday, August 3, 2011 12:15:32 PM UTC+2, Jorge wrote:
>> From http://en.wikipedia.org/wiki//dev/random : "The intent is to serve as a
>> cryptographically secure pseudorandom number generator, delivering output
>> with entropy as l
The missing HandleScope was leaking.
Thank you for pointing me to this collection of examples. (I prefer to use
a class for the Baton. It's more convenient.)
In my HelloWorld example, the AsyncA function does not include any blocking
operations, but during my next project I need the thread pool
A bit off topic because generators are not yet available in V8.
But if you are curious about how node.js async code could look like in the
future:
http://bjouhier.wordpress.com/2012/05/18/asynchronous-javascript-with-generators-an-experiment/
--
Job Board: http://jobs.nodejs.org/
Posting guide
If this is not fixed yet, you could move the hash to a thread_a_gogo so that
the hiccups won't happen in node's event loop thread, but in the thread_a_gogo.
You will still see delays when accessing the hash keys, but as the access to
the hash will be asynchronous they won't be blocking node.
Hi,
I'm also interested in this project.
Have a look on my framework [https://github.com/shogun147/Katana]
It could be good alternative to Express, especially for building such
project or any cms like solution.
Good luck!
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://git
Thanks Jorge, I turned off idle notifications and exposed the gc which runs
every 30 minutes or so. That's had a good impact on CPU across the whole
application. Then for the hash I switched to a Buffer backed hash
implementation. I can keep the per key memory overhead much lower like that
and
No i dont think, that's the way its done, since it would be very inefficient
and each chunk is converted to a string directly.
I Believe that string decoder checks the end of each chunk to see if any
multibyte char is straddling, very easy check in utf8 encoding, and excludes
the partial char
On 5/19/2012 6:20 AM, Bruno Jouhier wrote:
http://bjouhier.wordpress.com/2012/05/18/asynchronous-javascript-with-generators-an-experiment/
shouldn't that be print(num) not print(n)
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posti
Hi Graeme, indeed it's a RPC call to a program in Python. Dan, here is
the relevant code; User makes a HTTP request to /test and the program
sends a message to a python and returns the result to the user.
How do you think it would be the best implementation for this?
var connection = amqp.create
Ok, opened issue: https://github.com/joyent/node/issues/3286
Thanks!
On Thursday, May 17, 2012 4:48:16 PM UTC-4, Ben Noordhuis wrote:
> > Thanks, Ben. The patch applied fine to my v0.6.17-release branch, but
> > doesn't appear to have fixed the issue.
> >
> > (Also, 'make clean' doesn't seem
Yes, I fixed it. Thanks.
On Saturday, May 19, 2012 3:15:33 PM UTC+2, Matthew Hazlett wrote:
>
> On 5/19/2012 6:20 AM, Bruno Jouhier wrote:
> >
> http://bjouhier.wordpress.com/2012/05/18/asynchronous-javascript-with-generators-an-experiment/
>
>
> shouldn't that be print(num) not print(n)
>
>
I'm starting to implement file upload in my app (http://
outlinetracker.com/zapphotoshare/index.html). The "formidable" module
looks to be a good choice to handle the server-side details of the
upload process.
Obviously, I need to prevent the disk from being filled up with
uploads. Is there an A
How do you handle back pressure?
On May 19, 2012, at May 19, 20129:51 AM, Bruno Jouhier wrote:
> Yes, I fixed it. Thanks.
>
> On Saturday, May 19, 2012 3:15:33 PM UTC+2, Matthew Hazlett wrote:
> On 5/19/2012 6:20 AM, Bruno Jouhier wrote:
> > http://bjouhier.wordpress.com/2012/05/18/asynchronous
Yes, this thread will last until next year, when someone just tells us to
use the randomString() api and not try to reinvent the wheel.
On Sat, May 19, 2012 at 1:02 AM, Jorge wrote:
> On May 18, 2012, at 7:10 AM, Aleksander Adamowski wrote:
> > On Wednesday, August 3, 2011 12:15:32 PM UTC+2, Jo
So the "fast" way of converting a multi-buffer stream back into a string
would be to use string decoder, and convert each chunk, then concat the
strings right? In v8, the strings are actually cons-strings, so adding 2
strings together should be an O(1) operation right?
On Sat, May 19, 2012 at 5:
I'm not sure I get it but I'll try to answer.
What I'm describing in the post is how logic can be expressed with
generators rather than callbacks. I'm assuming that the low level calls are
callback-style. So, there is no reference to any specific I/O library
and/or to back pressure.
The back
On May 19, 2:41 pm, "P. Douglas Reeder" wrote:
> Obviously, I need to prevent the disk from being filled up with
> uploads. Is there an API to get disk space, or must I shell out and
> call "fs"? (My app runs on a linux device, specifically webOS 2.2 and
> higher.)
> Ishttp://groups.google.com/
On May 19, 2:41 pm, "P. Douglas Reeder" wrote:
> What other issues should I be concerned about in a production
> environment, and what's available in node to deal with them?
I'd also take "space free" with a grain of salt, especially if you
have multiple uploads going in parallel. I'd guess you'd
Would be nice if we had a module to take care of these things. A wrapper of
formidable that can keep track of the disk space and file extensions...
On Sunday, 20 May 2012 11:59:16 UTC+8, mscdex wrote:
>
> On May 19, 2:41 pm, "P. Douglas Reeder" wrote:
> > What other issues should I be concerned
19 matches
Mail list logo