On Tue, Aug 7, 2012 at 9:10 PM, Matt hel...@gmail.com wrote:
Did the libuv fix to not accept all incoming connections make it into this
one (the one to improve cluster load balancing)?
No, it only exists in master. It's commit 9f7cdb2[1] in case you want
to back-port it.
[1]
well done!
I know you guys are in the thick of it, and probably can't see the wood for
the trees, but-
I would suggest, NodeJS has a massive following in the x86, x64 area,
You probably have more (admittedly end-user types - not developers) people
interested in the ARM arena.
V8 needs to be
I would like to get linux-arm binaries up at some point, but they would
need to work on as many ARM devices as possible, and as Tim Caswell says,
portable arm binaries are an oxymoron. That said, if a copy of node
compiled for ARMv5 processors is the lowest common denominator for ARM
devices (I'm
If the binary package is an experimental feature, why was it introduced in
an even numbered release (stable)?
On Tuesday, August 7, 2012 3:06:36 PM UTC-4, Isaac Schlueter wrote:
2012.08.07, Version 0.8.6 (Stable)
This is the first release to include binary distributions for all
On Tue, Aug 7, 2012 at 3:07 PM, Bry brandon.add...@gmail.com wrote:
If the binary package is an experimental feature, why was it introduced in
an even numbered release (stable)?
Good question!
This is not really a feature of node itself, but just a feature of the
build process.
We've
Hi,
looking for for a mongdb client, any suggestions? not so particular
about ORM. thanks,
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
On Tue, Aug 7, 2012 at 8:30 AM, Angelo Chen angelochen...@gmail.com wrote:
Hi,
looking for for a mongdb client, any suggestions? not so particular
about ORM. thanks,
https://github.com/christkv/node-mongodb-native
http://mongodb.github.com/node-mongodb-native/api-articles/nodekoarticle1.html
https://github.com/LearnBoost/mongoose
On Mon, Aug 6, 2012 at 11:42 PM, Luca Morettoni l...@morettoni.net wrote:
On Tue, Aug 7, 2012 at 8:30 AM, Angelo Chen angelochen...@gmail.com
wrote:
Hi,
looking for for a mongdb client, any suggestions? not so particular
about ORM. thanks,
looking at mongojs and mongode, too many options for mongdb.
On Aug 7, 2:42 pm, Luca Morettoni l...@morettoni.net wrote:
On Tue, Aug 7, 2012 at 8:30 AM, Angelo Chen angelochen...@gmail.com wrote:
Hi,
looking for for a mongdb client, any suggestions? not so particular
about ORM. thanks,
We use mongoose and mongoskin for testing. It really depends on your
scenario. In general though mongoose is a good choice.
On Tue, Aug 7, 2012 at 12:44 AM, Angelo Chen angelochen...@gmail.comwrote:
looking at mongojs and mongode, too many options for mongdb.
On Aug 7, 2:42 pm, Luca
Hi Harsh,
I did not have the time/need to try that one out. threads_a_gogo
sounded the most useful though.
Jeremy
On 8/7/2012 2:49 AM, Harsh Dev wrote:
Hi Jeremy,
I've been looking into TAGG as well so if possible, could you give us
an overview of what your results are/were?
Thanks,
Axel, that's interesting. I was noticing the same issue, mainly that I have to
create uuid's in batches, in the browser, and Date.now() was not granular
enough, so they were all getting the same prefix. Didn't seem very useful.
Seems like there's no way to create strong, fast uuid's in the
If you can split your calculation to partials, like recursive approach, you
can use process.nextTick to execute the partial asynchronously. Check out
this example https://gist.github.com/3284767
Am Dienstag, 7. August 2012 11:28:23 UTC+2 schrieb Jeremy Rudd:
Hi Harsh,
I did not have the
On Tue, Aug 7, 2012 at 6:05 AM, Felix Halim felix.ha...@gmail.com wrote:
On Tue, Aug 7, 2012 at 3:47 AM, Ben Noordhuis i...@bnoordhuis.nl wrote:
No, libuv (and node.js) handles that fine. Chances are high that the
bug is in your application.
After further investigation, valgrind says that it
Hello Everyone,
Please suggest some javascript communities/groups to share a open source
project.
--
Cheers !!!
Ankur Agarwal
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you
It's only bad form if it doesn't fit your use case. Every situation
is different. That's the nature of software. I tend to write mostly
small libraries and micro-sites. Winston is overkill for me. I don't
know what's best for other people because I'm not in their shoes.
On Tue, Aug 7, 2012
Anyone know,
Are there any plans to update the RedHat/Fedora/CentOS package management
repos to the latest stable release?
While most might do development on other platforms (I don't), when
deploying Linux is the platform of choice.
Rob
--
Job Board: http://jobs.nodejs.org/
Posting
I prefer if you at least have a level of indirection away from console.log,
so that I can override it (or pass in a log function to a constructor of
some sort) without having to stomp on console.log.
On Mon, Aug 6, 2012 at 4:08 PM, kuhnza david.s.k...@gmail.com wrote:
One thing I am keen to
Just create an EventEmitter instance and emit your log events to there. People
who then want to have logging enabled can hook up their own logging library. Or
just listen to the emitted log messages using console.log
On Monday 6 August 2012 at 22:08, kuhnza wrote:
One thing I am keen to know
Hi,
I am using the following folder structure for an expressjs website:
/app.www
/app.uploads
I would like to use the static middleware to server the files in the
app.uploads folder, but with the following prefix: /uploads:
http://localhost:3000/b.jpg -- /app.www/b.jpg
On Tue, Aug 7, 2012 at 8:42 PM, Ben Noordhuis i...@bnoordhuis.nl wrote:
On Tue, Aug 7, 2012 at 6:05 AM, Felix Halim felix.ha...@gmail.com wrote:
On Tue, Aug 7, 2012 at 3:47 AM, Ben Noordhuis i...@bnoordhuis.nl wrote:
No, libuv (and node.js) handles that fine. Chances are high that the
bug is
I develop on linux and deploy to linux. I just use nvm to manage my
node versions. It's easy enough to get a compiler on all my
production boxes. Also I've heard rumors that nodejs.org will start
distributing node binaries for linux some time in the future.
On Tue, Aug 7, 2012 at 9:28 AM, Rob
On Tue, Aug 7, 2012 at 9:54 AM, Matt hel...@gmail.com wrote:
I prefer if you at least have a level of indirection away from console.log,
so that I can override it (or pass in a log function to a constructor of
some sort) without having to stomp on console.log.
The thing is, what is the purpose
Adam, which other ones do you recommend?
Gus
On Sun, Aug 5, 2012 at 7:41 PM, Adam Reynolds awjreyno...@gmail.com wrote:
I know this is slightly off-topic but why did you choose crafty over the
other game engine that are out there?
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
Well I looked at Crafty and it doesn't seem to support touch screen.
I don't think it's a wrong choice. I'm assuming you evaluated all of these
:)
EaselJS
ImpactJS
CraftyJS
MelonJS
Spaceport.io
LimeJS
On Tue, Aug 7, 2012 at 4:39 PM, Gustavo Machado machad...@gmail.com wrote:
Adam, which other
I am wondering which are the different patterns to handle cases like
var results
if (cond) {
async1(function (err, res) {
results = res
})
}
else {
async2(function (err, res) {
results = res
})
}
// here need to do something with results.
The problem is obvious, but i cannot
On Tue, Aug 7, 2012 at 11:35 AM, Dan Milon danmi...@gmail.com wrote:
I am wondering which are the different patterns to handle cases like
var results
if (cond) {
async1(function (err, res) {
results = res
})
}
else {
async2(function (err, res) {
results = res
})
}
//
On Tue, Aug 7, 2012 at 9:35 AM, Dan Milon danmi...@gmail.com wrote:
I am wondering which are the different patterns to handle cases like
var results
if (cond) {
async1(function (err, res) {
results = res
})
}
else {
async2(function (err, res) {
results = res
})
}
//
My use of UUIDs as DB keys has nothing to do with security. Just global
uniqueness. The term UUID doesn't imply any security.
On Mon, Aug 6, 2012 at 9:29 PM, Tim Caswell t...@creationix.com wrote:
Isaac is correct. Date.now is pretty guessable from a security standpoint
and so is
Thanks Tim. Based on what you're saying I'm leaning to just leaving the
console.log statements in there. Though, I'm a little unclear on how you'd
actually go about overriding console.(log|warn|error) etc. in client code.
Are you able to provide an example of how you'd do it?
Something like
True, that works on this simplified case, but there is more logic,
depending on the cond, etc.
I recall reading a blog post about having async if.
like
if (cond, trueFn, falseFn, doneFn)
That was interesting.
On 08/07/2012 07:47 PM, Mark Volkmann wrote:
On Tue, Aug 7, 2012 at 11:35 AM, Dan
Not a bad idea. Are you aware of any other libraries that do this? Trying
to gauge how common this approach is.
On Tuesday, August 7, 2012 7:59:10 AM UTC-7, 3rdEden wrote:
Just create an EventEmitter instance and emit your log events to there.
People who then want to have logging enabled can
To be truly compliant with the IETF specs, you cannot just use 128 random
bits because 6 bits are imposed in version 4 UUIDs:
Version 4 UUIDs have the form --4xxx-yxxx- where xis
any hexadecimal digit and
y is one of 8, 9, A, or B.
(from
Yeah that's exactly what I'm trying to avoid too Matt. I hate it when libs
indiscriminately fill up my logs with no easy way to control the
verbosity/formatting of their messages.
Is there anything like SLF4J for node? That way you could simply set the
logging implementation at the module
Nope most libs create their own logging libs or make it really hard to silence
the logs. Console log statements are a pita because as a developer you really
dont want to override build in functionality because some module is using that
as a logger
On 7 aug. 2012, at 18:55, kuhnza
I should mention that I only leave console.log statements in
production code for rare cases (like noting an http server was created
and is listening). I try to never do it in libraries I publish
because my users might not care about that information.
I like the idea of
I agree - it's not right. It's very annoying to have libraries do no
logging at all. It's fine when they work... but when they go wrong I want
logs!
On Tue, Aug 7, 2012 at 1:30 PM, kuhnza david.s.k...@gmail.com wrote:
That's my feeling also. Just did a quick survey of my node_modules folder
Found this discussion on the lists from last year:
https://groups.google.com/forum/?fromgroups#!topic/nodejs/YoHblrE8JJM but
it appears as though the discussion stalled.
One of the comments says it's pretty easy to re-route console output which
is true, but what do you do in the instance that
I've handled this by passing along what to do next to the async function:
var next = function(results) {};
if (cond) {
async1(next);
} else {
async2(next);
}
Easy to turn that into an asyncIf function if you find yourself doing
it frequently.
-- Daniel R. dani...@neophi.com
Here is one approach which is pretty interesting:
http://joseoncode.com/2012/06/24/messing-with-cps-in-js/
We are currently using iced-coffee-script in a project and I couldn't
be any happier, what you wrote would translate to:
if cod
await trueFn defer(err, result)
else
await falseFn
On Tue, Aug 7, 2012 at 1:58 PM, Tim Caswell t...@creationix.com wrote:
Matt, David,
Ignore what I said about how I use console.log, but what do you think
about TJ's debug library? To me it seems to solve your problems in a
really elegant way.
Yup absolutely. And I much prefer being able
Thanks Andreas!
It worked like a charm, I thought I had tried that already, but I must
have done something wrong.
Thanks,
Gus
On Tue, Aug 7, 2012 at 2:02 PM, papandreou
andreaslindpeter...@gmail.com wrote:
Hi Gus,
Use two instances of the express.static middleware:
var path =
debug is quite okay, but again, the problem with it is that you cannot supply
it your own logging
instance, it writes it to console.log and console.error.
On Tuesday, August 7, 2012 at 7:58 PM, Tim Caswell wrote:
Matt, David,
Ignore what I said about how I use console.log, but what do you
TJ's lib looks alright, having the option to control via environment
variables is probably an acceptable solution.
This discussion has led me to delve a little deeper into the winston source
code and I think there's a problem there for which I've raised an
issue/pull request on GitHub
Pattern 1:
if (cond) results = async1(_);
else results = async2(_);
Pattern 2:
results = cond ? async1(_) : async2(_);
See https://github.com/Sage/streamlinejs for details.
On Tuesday, August 7, 2012 6:35:20 PM UTC+2, Dan Milon wrote:
I am wondering which are the different patterns to
2012.08.07, Version 0.8.6 (Stable)
This is the first release to include binary distributions for all
supported Unix operating systems (Linux, Darwin, and SunOS). To use
the binary distribution tarballs, you can unpack them directly into a
destination directory:
cd ~/node/ # or /usr/local if
Did the libuv fix to not accept all incoming connections make it into this
one (the one to improve cluster load balancing)?
On Tue, Aug 7, 2012 at 3:06 PM, Isaac Schlueter i...@izs.me wrote:
2012.08.07, Version 0.8.6 (Stable)
This is the first release to include binary distributions for all
On 08/07/2012 01:48 AM, Martin Wawrusch wrote:
We use mongoose and mongoskin for testing. It really depends on your
scenario. In general though mongoose is a good choice.
it is if you want to specify schema or use ORM - otherwise
mongo-node-native is the defacto node mongo driver and works
Hi Tim.
Thanks for the note. Nodejs.org already has
binarieshttps://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager.
My complaint is they are old.
I'll look into nvm.
Rob
On Tuesday, August 7, 2012 9:25:29 AM UTC-6, Tim Caswell wrote:
I develop on linux and deploy to
On Tue, Aug 7, 2012 at 2:23 PM, Rob Hicks r...@hixfamily.org wrote:
Hi Tim.
Thanks for the note. Nodejs.org already has binaries. My complaint is they
are old.
The binaries I was speaking of are in the dist folder. They are quite
fresh, I assure you. http://nodejs.org/dist/
I'll look into
On Tue, Aug 7, 2012 at 8:06 PM, Isaac Schlueter i...@izs.me wrote:
2012.08.07, Version 0.8.6 (Stable)
This is the first release to include binary distributions for all
supported Unix operating systems (Linux, Darwin, and SunOS).
Nice!
The SunOS binaries are only for modern versions
That looks like a compile error. What does the stack trace look like? I
doubt the error is coming from server.js
On Tuesday, August 7, 2012 12:39:28 PM UTC-7, yishayw wrote:
Hi,
I have a site which uses a library with a static file named server.js.
Node.js seems to be treating this as a
Hi all,
webinos is a cross device platform built entirely on top of node js and is
organizing an application competition so I thought of sharing this with you
just in case you want to do a summer project and win some cool prizes.
More info at http://bit.ly/webinoscomp
Thanks in advance for
On Tue, Aug 07, 2012 at 01:10:39PM -0700, Andreas M. Botsikas wrote:
Hi all,
webinos is a cross device platform built entirely on top of node js and is
organizing an application competition so I thought of sharing this with
you just in case you want to do a summer project and win
well done!
I know you guys are in the thick of it, and probably can't see the wood for
the trees, but-
I would suggest, NodeJS has a massive following in the x86, x64 area,
You probably have more (admittedly end-user types - not developers) people
interested in the ARM arena.
V8 needs to be
I would like to get linux-arm binaries up at some point, but they would
need to work on as many ARM devices as possible, and as Tim Caswell says,
portable arm binaries are an oxymoron. That said, if a copy of node
compiled for ARMv5 processors is the lowest common denominator for ARM
devices (I'm
honestly - my preference is for the A10 (or A13) chip
you can load linux - then nodejs then you js code onto a memory stick and
the A10 boots from the stick (either USB or SD)
The A10 is available in a number of tablets, and the brilliant MK802 stick.
If you want a device to try it on - tell me
I would personally go with using promises.
var q = require('q');
q.ncall(function() {
if(cond) {
return async1(); // this is a promise
}
return async2(); // so is this
}).then(function(res) {
// hooray! one of them finished
}).error(function(res) {
// something went
Hi guys, I have updated the code. Now, it is not just a memory store. With
LRU code added, it become a real Cache Daemon.
You can review the code here: https://gist.github.com/3291755
It still has many places to improve. Any idea to improve the LRU algorithm
or memory management? please let me
59 matches
Mail list logo
