[nodejs] Re: The Future of Programming in Node.js

Any mention about changes in HTTP core module? A couple of months ago you (Isaac) had a talk where you said that there are some rooms (and plans) for rewriting HTTP core-module as well as current Buffer implementation. And the second question is about NPM. Are there similar long running plans f

[nodejs] Re: The Future of Programming in Node.js

On Tuesday, August 13, 2013 3:29:12 PM UTC-7, Rouan van der Ende wrote: > Thank you Isaac, and all node contributors. > I am glad the focus is now on refinement and longevity in a non-breaking > way. You mention performance improvement and I am curious how much there is > left to squeeze out an

[nodejs] Best practices managing node dependencies?

Hi, I would like to hear from others how npm dependencies are managed. I am typically doing this: - use npm shrink wrap - check in to git only that file but not the modules - once per iteration check for updates to all modules and decide to update or not The issues I am seeing with this approac

[nodejs] Re: set timeout for a mysql query in node js

Hi Juilee, You can override the default connection timeout http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html This however should be a temporary fix/alternative. Do consider sharding on a mysql cluster ( http://www.mysql.com/products/cluster/scalability.html) Thanks, Chris

[nodejs] Submitting a form

I have successfully requested a page with the http module. There is a form I'd like to fill out on the page, how do you fill it out and then send it back to the server? -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidel

Re: [nodejs] Re: The Future of Programming in Node.js

On Tue, Aug 13, 2013 at 3:42 PM, Nuno Job wrote: > While I agree with the sentiment in most of this email I would argue Streams > are not backward compatible. There's an effort so that what was coded in 0.8 > still works in 0.10, but it's impossible to code things that work in both > 0.8 and 0.10

[nodejs] Re: The Future of Programming in Node.js

I'm glad that people like Isaacs are leading the charge here instead of some of these wild opinions being thrown about on this list. I think that I speak for a silent majority when I say that I honestly don't understand why people say that callbacks are the root of all evil. Callbacks are amazi

Re: [nodejs] Re: The Future of Programming in Node.js

I agree with Issacs and Bert. We should have node as it is. Error handling and callbacks are sucks. (for most/some of the people). But still we build apps. As bert said, we need solutions for those problems. Fibers, promises does a good job. It need to be better. Meteor is a good example, which t

Re: [nodejs] Re: The Future of Programming in Node.js

On Aug 13, 2013, at 6:07 PM, Mikeal Rogers wrote: > > In the end, all of this mailing list complaining doesn't really amount to > anything. While several of the most vocal people here put their code where > their mouth is and maintain libraries for alternatives to node's core > patterns most o

Re: [nodejs] BREACH and node.js ( 2013 Black Hat conference )

On 13 August 2013 at 8:54:30 PM, Ryan Schmidt (google-2...@ryandesign.com) wrote: On Aug 13, 2013, at 19:50, Aria Stewart wrote:  > It’s a systemic flaw in the way that compression interacts with encryption. > The best ways to defeat it are to make your compression unpredictable to an > order

Re: [nodejs] Keep data in memory and periodlly push to mongodb ???

Depends on what it is you want to actually accomplish... Honestly, MongoDB is pretty decent, and if the majority of your active data fits in memory, those pages in Mongo will be readily available. I would suggest starting by targeting mongo directly if that’s your desired back end... otherwise

Re: [nodejs] BREACH and node.js ( 2013 Black Hat conference )

On Aug 13, 2013, at 19:50, Aria Stewart wrote: > It’s a systemic flaw in the way that compression interacts with encryption. > The best ways to defeat it are to make your compression unpredictable to an > order of magnitude that outstrips the ability to guess what the content is by > how it’s

Re: [nodejs] BREACH and node.js ( 2013 Black Hat conference )

On 13 August 2013 at 8:47:04 PM, Ryan Schmidt (google-2...@ryandesign.com) wrote: On Aug 13, 2013, at 07:16, Chris Wakare wrote:  > During the 2013 Black Hat conference , researchers announced the BREACH > attack. As BREACH takes advantage of vulnerabilities when serving compressed > data over

Re: [nodejs] BREACH and node.js ( 2013 Black Hat conference )

On Aug 13, 2013, at 07:16, Chris Wakare wrote: > During the 2013 Black Hat conference , researchers announced the BREACH > attack. As BREACH takes advantage of vulnerabilities when serving compressed > data over SSL/TLS, its been advised to disable compression of web responses. > > I see thi

Re: [nodejs] The Future of Programming in Node.js

I've heard people complaining about things in node sucking pretty much since day 1, but then complaints are usually louder than compliments. On Tuesday, 13 August, 2013 at 4:27 PM, Mark Hahn wrote: > > I'd be interested in seeing the data your referencing. > > Ok, a statistical assumption based

Re: [nodejs] The Future of Programming in Node.js

> I'd be interested in seeing the data your referencing. Ok, a statistical assumption based on experience. If a lot of people say it sucks then it probably sucks. If just a few say so then it probably doesn't. I've been reading this discussion group religiously for over two years and I've not h

[nodejs] Keep data in memory and periodlly push to mongodb ???

Hi everyone, I'm doing a realtime game by javascript and node.js. I want to all the informations is saved in memory of machine (RAM) and periodly (for example 10 minutes), it pushs data to mongodb So if you want to search smt, if this thing is not in memory of machine and I search in mongodb.

Re: [nodejs] The Future of Programming in Node.js

On Tuesday, August 13, 2013, Mark Hahn wrote: > > Sure. Always follow the majority rule! > > I wasn't saying anything about what action to take. I was just stating a > statistical fact. > I'd be interested in seeing the data your referencing. Rick > On Tue, Aug 13, 2013 at 3:40 PM, Bruno Jo

Re: [nodejs] Announcing naught 0.6.0

thanks Andrew! On Tue, Aug 13, 2013 at 5:51 PM, Andrew Kelley wrote: > Sure, does this help? > > What forever does that naught doesn't do: > >- supports having a delay before restarting server to avoid spinning >- option to not run server forever >- ability to watch server and auto

Re: [nodejs] Re: The Future of Programming in Node.js

> Sure. Always follow the majority rule! I wasn't saying anything about what action to take. I was just stating a statistical fact. On Tue, Aug 13, 2013 at 3:40 PM, Bruno Jouhier wrote: > > Not true. When someone (or even a few) say it sucks and no one agrees >> then he is usually wrong. >> >

Re: [nodejs] Re: The Future of Programming in Node.js

While I agree with the sentiment in most of this email I would argue Streams are not backward compatible. There's an effort so that what was coded in 0.8 still works in 0.10, but it's impossible to code things that work in both 0.8 and 0.10 without different code. Might seem minor, but since I foun

Re: [nodejs] Re: The Future of Programming in Node.js

> Not true. When someone (or even a few) say it sucks and no one agrees > then he is usually wrong. > Sure. Always follow the majority rule! Even if you think it sucks, it really doesn't! "Suddenly, I do not know how, it happened, I did not have time to think, Panurge, without another word

[nodejs] Re: The Future of Programming in Node.js

Thank you Isaac, and all node contributors. I am glad the focus is now on refinement and longevity in a non-breaking way. You mention performance improvement and I am curious how much there is left to squeeze out and where do you think the gains are to be made? On Tuesday, 13 August 2013 19:57:

[nodejs] Re: The Future of Programming in Node.js

What matters most to me at this stage is: * Robustness * Robustness * Robustness * Robustness * Robustness * Performance * Performance * Performance * Performance * Backward compatibilty * Backward compatibility * Backward compatibility * New platforms (AIX would be cool but we can do without). J

[nodejs] Re: The Future of Programming in Node.js

> > > *Forking is not an option* > > *There are not so much insane people* > These two points are in conflict with each other. Either there's critical mass for forking or there is not. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-

Re: [nodejs] Re: The Future of Programming in Node.js

There will always be people who don't like a particular decision in the core API. There are problems/bugs that are being fixed and there are others that are unlikely to change in core because they would break compatibility (which node can no longer tolerate). In the end, all of this mailing li

Re: [nodejs] Re: The Future of Programming in Node.js

> If someone tells that the core API sucks probably it's really sucks Not true. When someone (or even a few) say it sucks and no one agrees then he is usually wrong. On Tue, Aug 13, 2013 at 2:50 PM, Eldar wrote: > >This is not a democracy. However, there's plenty of room for > >everyone's opi

[nodejs] Re: node.js support on windows 8

Which node version are you using? I am using 0.8.19 64bit and behind a firewall as well with no issues. - Chris On Friday, August 9, 2013 5:42:39 PM UTC+5:30, hemant bhatt wrote: > > Hi, > I installed 32 bit node.js on my windows 7 machine and hosted a web server > using the sample available

Re: [nodejs] Announcing naught 0.6.0

Sure, does this help? What forever does that naught doesn't do: - supports having a delay before restarting server to avoid spinning - option to not run server forever - ability to watch server and auto restart - has a lot of bugs

[nodejs] Re: The Future of Programming in Node.js

>This is not a democracy. However, there's plenty of room for >everyone's opinion. If you want to make exciting dramatic breaking >changes to node-core, and you can't find satisfaction by writing >userland npm modules, then please fork joyent/node, give it a new name >and logo, and go as complete

Re: [nodejs] Announcing naught 0.6.0

This looks awesome, I was actually just looking for things like this to keep my web server running. However, I also found this https://github.com/nodejitsu/forever Could you give me brief pros and cons between the two? in terms of keep the scripts/server running. thanks On Tue, Aug 13, 2013 at

[nodejs] Re: The Future of Programming in Node.js

On Tuesday, August 13, 2013 10:57:44 AM UTC-7, Isaac Schlueter wrote: > > Streams are more consistent, faster, and 100% backwards compatible as > of 0.10. The "compatibility mode" aka "old mode" is folded into the > API more cleanly. You can `pause()` a flowing stream, and then start > callin

[nodejs] Re: The Future of Programming in Node.js

On Tue, Aug 13, 2013 at 12:15 PM, Bert Belder wrote: > * People might have found some 'pain killer' patterns to deal with callback > hell. However that doesn't mean there isn't a real solution for this. When and if a clear winner arises from userland, if it can be merged into core without breakin

[nodejs] Announcing naught 0.6.0

Hey guys, I just released naught 0.6.0 which is much more user-friendly than previous releases. Give it a shot! naught - zero downtime deployment for your node.js server using native cluster api Features - Run multiple workers which listen on the same

[nodejs] Re: The Future of Programming in Node.js

See my topic, about the yielded style programming... and say goodbye to the callback hell. ;) -- -- 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 Grou

Re: [nodejs] BREACH and node.js ( 2013 Black Hat conference )

Hi, I was referring to the practice of using http://nodejs.org/api/zlib.html for compression. You can see even ExpressJS implement the same. - Chris On Wednesday, August 14, 2013 1:55:04 AM UTC+5:30, Ben Noordhuis wrote: > > On Tue, Aug 13, 2013 at 2:16 PM, Chr

Re: [nodejs] OOP in Node.js ???

John, you do not have to do any this/that dance thing, you just have to understand how this works, and by this I mean both, "this" and JavaScript. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this

[nodejs] set timeout for a mysql query in node js

Hello, I am referring to this post on stackoverflow. http://stackoverflow.com/questions/14406488/node-js-mysql-query-timeout I am using node for server-side scripting and my web application is connected to a MySQL database. The database has tables having around 60 million rows. I have the need

Re: [nodejs] Load on node-server

On Tue, Aug 13, 2013 at 5:04 PM, Jens Himmelreich wrote: > > Am Montag, 12. August 2013 19:03:27 UTC+2 schrieb Ben Noordhuis: >> >> On Mon, Aug 12, 2013 at 6:05 PM, Jens Himmelreich >> wrote: >> > Hi, >> > >> > I have a node-server between an nginx-webserver (static content) and an >> > varnish.

Re: [nodejs] BREACH and node.js ( 2013 Black Hat conference )

On Tue, Aug 13, 2013 at 2:16 PM, Chris Wakare wrote: > Hello, > > During the 2013 Black Hat conference , researchers announced the BREACH > attack. As BREACH takes advantage of vulnerabilities when serving compressed > data over SSL/TLS, its been advised to disable compression of web responses. >

Re: [nodejs] setTimeout and setInterval issue when wall clock changes

On Tue, Aug 13, 2013 at 4:30 PM, Criton wrote: > Hi all. > I am running nodejs 0.10.15 on an ubuntu 12.04 machine. > I wrote a simple js module, for clock behaviour testing: > > setInterval(function () { > console.log("Now: " + Date.now()); > }, 2000); > > On console I see every 2 seconds (more or

Re: [nodejs] OOP in Node.js ???

This is one of the main reaons I prefer to write my code in Coffeescript. You don't have to do the this/that dance thing. You just use the => notation to define functions. On Tuesday, August 13, 2013 1:34:57 AM UTC-7, bodo wrote: > > Thank you guy > > On Tuesday, August 13, 2013 2:46:55 AM UTC

[nodejs] Re: The Future of Programming in Node.js

Agree that not breaking node apps and modules is a good thing. However, as long as node is relevant, we shouldn´t stop innovating. I mean, * People might have found some 'pain killer' patterns to deal with callback hell. However that doesn't mean there isn't a real solution for this. * Error

[nodejs] Re: The Future of Programming in Node.js

To clarify one point: >>> Streams are more consistent, faster, and 100% backwards compatible as of 0.10. >>> What I mean is, v0.12 is 100% backwards compatible to v0.10. On Tue, Aug 13, 2013 at 10:57 AM, Isaac Schlueter wrote: > There's been a lot of debates, theories, and requests about Node'

[nodejs] The Future of Programming in Node.js

There's been a lot of debates, theories, and requests about Node's core API patterns on this list lately. I'd like to clarify the actual plans of the project on these points. Callbacks will remain the de facto way to implement asynchrony. Generators and Promises are interesting and will remain a

Re: [nodejs] Re: Opinion about TypeScript

> if you're in a team, stick to its style. And likewise, if you're in a team, stick to its language. I pick projects based on how cool and useful they are. I can't imagine avoiding the next big thing (like node) because it is programmed in Java. On Tue, Aug 13, 2013 at 1:06 AM, greelgorke

Re: [nodejs] What was the build system for the node.js binary packages?

Thank you both for this detailed information. I would suggest to put it at least to the Wiki (on GitHub) or next to builds on the downloads page as a footprint. Just as I said, compiling on low resource machines isn't that much fun. I think, that's why these binary builds are generally a great

Re: [nodejs] Load on node-server

Am Montag, 12. August 2013 19:03:27 UTC+2 schrieb Ben Noordhuis: > > On Mon, Aug 12, 2013 at 6:05 PM, Jens Himmelreich > > wrote: > > Hi, > > > > I have a node-server between an nginx-webserver (static content) and an > > varnish. > > Behind the varnish are two application-server for search

Re: [nodejs] Dependencies for native module installs via npm/node-gyp (especially when offline)

Ben, On Aug 13, 2013, at 1:03 AM, Ben Noordhuis wrote: > On Tue, Aug 13, 2013 at 5:45 AM, andy e wrote: >> When trying to install leveldown/levelup on Windows using node 0.10.9 & npm, >> npm/node-gyp grabs dependencies from http://nodejs.org/dist/> version here>/ >> i.e. http://nodejs.org/dist/

[nodejs] setTimeout and setInterval issue when wall clock changes

Hi all. I am running nodejs 0.10.15 on an ubuntu 12.04 machine. I wrote a simple js module, for clock behaviour testing: setInterval(function () { console.log("Now: " + Date.now()); }, 2000); On console I see every 2 seconds (more or less) appearing something like 'Now: 137840305890' (obviously

Re: [nodejs] Re: An Erlang-like "process" model for Node.js

On Tue, Aug 13, 2013 at 12:08 AM, Tristan Slominski < tristan.slomin...@gmail.com> wrote: > > >> With the design I'm proposing, creating an actor will spawn a new thread >> with its own event loop waiting to receive messages. I'm not sure on the >> cost of that, but it would be interesting to fin

[nodejs] BREACH and node.js ( 2013 Black Hat conference )

Hello, During the 2013 Black Hat conference , researchers announced the BREACH attack. As BREACH takes advantage of vulnerabilities when serving compressed data over SSL/TLS, its been advised to disable compression of web

Re: [nodejs] Re: The future of node streams. We need to talk

>However, the end result is a higher level abstraction of streams that should live in user land not core. The end result is not a higher level abstraction just because you can convert simple-stream to 100% compatible core stream and vice versa. >I would argue this is an education problem, not a

[nodejs] Re: How do I add numbers to output?

this should do: tracerute = require('traceroute'); traceroute.trace('4.69.155.254', function (err,hops) { if (err) console.error(err) else hops.forEach(function(hop, index){ console.log(index + 1, hop) }); }); if you whant to transform your data and save the transformed res

[nodejs] How do I add numbers to output?

Hi, How should I think (and do) to add numbers to each hop (line) on my traceroute. Here is my script (it's example script from traceroute npm package) traceroute = require('traceroute'); traceroute.trace('4.69.155.254', function (err,hops) { if (!err) console.log(hops);}); And output is l

[nodejs] Re: The future of node streams. We need to talk

Sure but while we are talking about fixing stuff.. On Tuesday, August 13, 2013 10:16:01 PM UTC+12, Eldar wrote: > > Than don't pass them to multiple readers? > > вторник, 13 августа 2013 г., 8:23:25 UTC+4 пользователь Jakeb Rosoman > написал: >> >> Aren't simple-stream's still a bit problematic i

Re: [nodejs] Re: The future of node streams. We need to talk

> file.pipe(res) > file.on('error', res.destroy.bind(res)) > res.on('error', file.destroy.bind(res)) > What is wrong with this? I don't see an issue with streams/pipe. You could argue that docs and tutorials need to be clearer about error handling. I would argue this is an education problem,

[nodejs] Re: The future of node streams. We need to talk

Than don't pass them to multiple readers? вторник, 13 августа 2013 г., 8:23:25 UTC+4 пользователь Jakeb Rosoman написал: > > Aren't simple-stream's still a bit problematic if you pass them around > like values? Because multiple readers would still interfere with each other > wouldn't they? > >

[nodejs] Re: The future of node streams. We need to talk

file.pipe(res) On response error (say client clicked close window button) the file will remain open. And vice versa on file error response will hang. So the correct way to pipe is file.pipe(res) file.on('error', res.destroy.bind(res)) res.on('error', file.destroy.bind(res)) вторник, 13 августа

Re: [nodejs] Re: An Erlang-like "process" model for Node.js

[resending with e-mail address subscribed to nodejs mailing list] 2013/8/12 Mark Miller > [+cutsem, +btulloh] > > Hi Tristan, you may be interested in a recent paper on Dr. SES by Tom Van > Cutsem, Bill Tulloh, and myself: < > http://research.google.com/pubs/pub40673.html>. In it we explain our

[nodejs] Re: The future of node streams. We need to talk

ok. I didn't understand the part about " `.pipe()` doesn't cleanup any resources. Everything works fine until the streaming process completes successfully. " Is there an example where that becomes obvious? On Monday, 12 August 2013 18:05:02 UTC+2, Eldar wrote: > > If you want to create some fun

Re: [nodejs] OOP in Node.js ???

Thank you guy On Tuesday, August 13, 2013 2:46:55 AM UTC+2, Rick Waldron wrote: > > `this.collection` doesn't yet exist, so the `else` path in `saveData` is > being taken, which is sent to `connectDB` which calls > `MongoClient.connect`, but does not bind `this` to the callback. > > This change

Re: [nodejs] Re: Opinion about TypeScript

a programmer shouldn't mind to progam in different languages. but, its the same as with coding style: if you're in a team, stick to its style. and if you open source something, then stick to the style/lang of the target community. in node vanila js is the main language. of course you can openso

Re: [nodejs] What was the build system for the node.js binary packages?

> > TJ Fontaine is the ultimate authority on this subject but I believe > the last few releases were compiled on a CentOS 6 box. > > We're in the process of changing that to CentOS 5.x to make the > binaries compatible with old versions of glibc*. IIRC, they're > currently linked against glibc 2.1

Re: [nodejs] What was the build system for the node.js binary packages?

On Tue, Aug 13, 2013 at 5:16 AM, Matthias Dittgen wrote: > Hello, > > compiling node directly on a VPS with only few resources for every new > version was very time consuming. > Thus I now install the binary package using my own fork of a really nice > install script (https://gist.github.com/matth

Re: [nodejs] Dependencies for native module installs via npm/node-gyp (especially when offline)

On Tue, Aug 13, 2013 at 5:45 AM, andy e wrote: > When trying to install leveldown/levelup on Windows using node 0.10.9 & npm, > npm/node-gyp grabs dependencies from http://nodejs.org/dist/ version here>/ > i.e. http://nodejs.org/dist/v0.10.9/node-v0.10.9.tar.gz > > This was on an offline (no Inter