Hi,
each option in the database space is good at different things and have very
different usage profiles. The most important question you have to answer
before you even think of which DB system to use or whether you even want to
use one at all is:
What is my data and access profile.
For
It sounds like you don't habe to load all files on startup, but do so in order
to not block later. So maybe your solution is to only require what is needes at
start and then switch to async require.
I wrote an async require last week as a test. Since you can in fact
require('module') and
It sounds like you don't habe to load all files on startup, but do so in order
to not block later. So maybe your solution is to only require what is needes at
start and then switch to async require.
I wrote an async require last week as a test. Since you can in fact
require('module') and
It sounds like you don't habe to load all files on startup, but do so in order
to not block later. So maybe your solution is to only require what is needes at
start and then switch to async require.
I wrote an async require last week as a test. Since you can in fact
require('module') and
It sounds like you don't habe to load all files on startup, but do so in order
to not block later. So maybe your solution is to only require what is needes at
start and then switch to async require.
I wrote an async require last week as a test. Since you can in fact
require('module') and
Hi,
I am also constantly living in bugger (great work Jan!). I am currently
looking into extending it to provide saving of local changes.
Also bugger does writes to disconnected web-sockets if you do a reload of
the dev-tools which is sometimes necessary when more sourcefiles get add
via
d) I use it a lot and find the strangeness of binary strings so dumb that
I'd rather have it changed sooner or later even if that means having to
rewrite/modify a bit of code.
On Tuesday, October 9, 2012 1:24:36 AM UTC+2, Isaac Schlueter wrote:
Currently, the crypto module defaults to using
Look people, think of the context of the statements he made. I think he
gave huge kudos to node.
I wrote a longer post on that (and this thread) as well:
http://instarant.net/crockford-right-nodejs-joyent
Regards, Philipp
On Saturday, September 15, 2012 4:45:30 PM UTC+2, Jorge wrote:
Hi,
I am really liking the new domains feature. However I have a question: How
do I leave a domain
Is my undesrtanding correct?:
function b(callback) {
// I am running inside the domain created in a
fs.readFile('some-file', 'utf-8', function(err, val) {
// I am running
Hi all,
I just published a module that is a simple http server that forwards to
https. Nothing spectacular, but since it is something that almost all my
projects need, I figured packaging it and making it available might be a
good thing.
Regards,
phidelta
--
Job Board: http
as well.
Regards,
phidelta
--
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
Hi,
I am currently experimenting with domains in a storage-library that
provides me with a uniform interface to s3, memcache, files, mongo, et. al.
It is an awesome feature, that allows for much easier error handling and
enables me to centralize error-reporting in a structured and easy way.
Hi,
I am currently experimenting with domains in a storage-library that
provides me with a uniform interface to s3, memcache, files, mongo, et. al.
It is an awesome feature, that allows for much easier error handling and
enables me to centralize error-reporting in a structured and easy way.
If
setTimeout(foo.func.bind(foo), 1000) is so drastically slower than
setTimeout(foo.func, foo, 1000) then our aim for the benefit of the
language should be to improve the performance of bind(). A lot of
scenarios would benefit from improved bind() performance and we should
not create kludge for
Hi all,
I have recently come to use .bind a lot, because it makes for very
clean code.
So rather than doing
code
var x; // this has some value that comes from prior code
setTimeout(function() { console.log(x) }, 5000);
/code
I am now often doing
code
var x;
The problem with doing this via npm is that npm works with the
dependencies from the package.json which is a problem for plugins,
since they are seldom known at the time the package.json is writeen.
I have done something like this for my app. What I ended up doing is
simply defining a folder
Hi Isaac,
this would make a great addition to the Buffer documentation. I did
not think of that and I actually read the node source code. It's
obvious once you point it out though. Maybe a hint in the docs would
be a Good Thing™.
On Mar 15, 8:09 pm, Isaac Schlueter i...@izs.me wrote:
+1 What
Oh and yes, you are absolutely on the right track. NODE_CHANNEL_FD
signals that the stein is an IPC Pipe and that is handled in src/
node.js cluster.js simply uses child_process.js to establish children.
net.js is where the funky listening port sharing stuff happens.
The cop pie wrapping is the
The king is dead; Long live the king!
Thanks to your great leadership, this will not negatively impact the
vibrant nodejs community. It will however positively impact the
personal satisfaction with your daily tasks. So I congratulate you
from the bottom of my heart. Let's have an adequate period
19 matches
Mail list logo
