gmane.comp.lang.javascript.nodejs

RE: Re: Retrieving values asynchroniously

Peter Rust — 2013-05-23T20:21:17

There's also nipster (http://jiyinyiyong.github.io/nipster/), which combines
github rankings with npm packages.

Re: Re: Retrieving values asynchroniously

Mark Hahn — 2013-05-23T18:46:38

The most_watched <https://github.com/languages/JavaScript/most_watched> list
is awesome. Thanks for the tip.


On Thu, May 23, 2013 at 8:42 AM, Alexey Petrushin <
alexey.petrushin-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

Re: Re: trying to wrap my head around "promises" - async vs Q

Baz — 2013-05-23T18:05:40

Thank you gents, perfectly got it now.


On Thu, May 23, 2013 at 10:42 AM, // ravi <ravi-lists-EmknxpygJzU< at >public.gmane.org> wrote:

Re: Re: trying to wrap my head around "promises" - async vs Q

// ravi — 2013-05-23T17:42:56

Q provides you mechanisms to wrap non-promise returning calls (for both async/blocking/callback scenarios and — this is very useful — for functions that return immediately as well). If you are looking at these sort of libraries, I also heartily recommend Flow, which has the easiest learning curve IMHO: https://github.com/willconant/flow-js.

—ravi

RE: Re: trying to wrap my head around "promises" - async vs Q

Domenic Denicola — 2013-05-23T17:32:25

That's overstating it a bit. It's very easy to convert to promise-based code, e.g.:

var fs = require('fs');
var Q = require('q');

var readFile = Q.denodeify(fs.readFile);
var writeFile = Q.denodeify(fs.writeFile);

readFile('src.txt').then(function (result) { writeFile('dest.txt', result); }).done();

Since this conversion process is pretty mechanical, there are several libraries that have done it for you, e.g. https://npmjs.org/package/pr

________________________________
From: nodejs-/JYPxA39Uh5TLH3MbocFFw< at >public.gmane.org [nodejs-/JYPxA39Uh5TLH3MbocFFw< at >public.gmane.org] on behalf of Baz [bk< at >thinkloop.com]
Sent: Thursday, May 23, 2013 13:28
To: nodejs-/JYPxA39Uh5TLH3MbocFFw< at >public.gmane.org
Subject: Re: [nodejs] Re: trying to wrap my head around "promises" - async vs Q

Thanks Matt, so just to be crystal clear, if I'm using promises in my own code, then I happen to have a flow that depends on fs, for example, and since fs doesn't return or use promises, I would have to drop out of the promises paradigm a

Re: Re: trying to wrap my head around "promises" - async vs Q

Baz — 2013-05-23T17:28:07

Thanks Matt, so just to be crystal clear, if I'm using promises in my own
code, then I happen to have a flow that depends on fs, for example, and
since fs doesn't return or use promises, I would have to drop out of the
promises paradigm and manage that particular part of the flow control with
callbacks or something like asynch?


On Thu, May 23, 2013 at 7:01 AM, Matt <helpme-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

Re: Newbie question here

mscdex — 2013-05-23T16:03:32

Just look at the order of your `app.use()` calls.

According to passport's site, the order should be something like this:

app.configure(function() {
  app.use(express.static('public'));
  app.use(express.cookieParser()); // first
  app.use(express.bodyParser());
  app.use(express.session({ secret: 'keyboard cat' })); // second
  app.use(passport.initialize()); // third
  app.use(passport.session()); // fourth
  app.use(app.router); // fifth
});

Re: Re: Retrieving values asynchroniously

Alexey Petrushin — 2013-05-23T15:42:12

The best rating I know https://github.com/languages/JavaScript/most_watched

By the way, not only for JS but for other langs too, usually, when I need 
something and don't know where to start - I start there, and after reading 
3-10 pages found all major solutions for my problem.

I don't like "mentored/opinionated" ratings, usually they are either too 
small and don't include all the possibilities or outdated or not objective 
or your opinion don't match with the opinion of those who mentor it :)

Re: Newbie question here

Toddy Mladenov — 2013-05-23T15:35:19

I am not. Can you give me some hints what this session middleware should be?

On Wednesday, May 22, 2013 5:25:54 AM UTC-7, mscdex wrote:

Re: node-v0.6.18 http module the submitted url with Chinese parameter under ie9 does not recognize

Ryan Schmidt — 2013-05-23T15:04:39

On May 23, 2013, at 02:37, cheng cao wrote:


That's old. Please try 0.10.7.

Re: Re: trying to wrap my head around "promises" - async vs Q

Matt — 2013-05-23T14:01:02


I think the problem with promises is that the core node libraries aren't
implemented with promises, so if you need to do a series of e.g. fs calls
(typical example might be open, then stat, then create a readStream from
the fd) you wind up using async anyway, or manually coding up the nested
callbacks, which can feel ugly once you've started using a particular flow
control library. And then once you start using async for one thing, it just
starts to feel natural. It just fits so perfectly with the Node ecosystem.

In short: There's nothing wrong with the promises model (although I find it
overly verbose), it's just that async fits better with node libraries.

Matt.

Re: Correct use of HandleScope in an asynchronous node addon

Ben Noordhuis — 2013-05-23T13:41:47

Yes.  Rule of thumb: any function that manipulates V8 values somehow,
needs a HandleScope.


No, V8 takes care of that.

A Local<> is a reference to a JS value that is rooted in the current
HandleScope.  When you call a JS function, and when that function
takes out an additional reference on the value, V8 "knows" about it.
It won't garbage-collect the value until there are no more references.

node-v0.6.18 http module the submitted url with Chinese parameter under ie9 does not recognize

cheng cao — 2013-05-23T07:37:51

the code:

var http = require('http');
http.createServer(function (req, res) {
  console.log(req.url);
  res.writeHead(200, {'Content-Type': 'text/plain'});
  res.end('Hello World\n');}).listen(1337);
console.log('Server running at 1337');

I install the node-v0.6.18 on window7 and linux
cat /etc/issue
Red Hat Enterprise Linux AS release 4 (Nahant Update 8)
Kernel \r on an \m
the submit url is "http://127.0.0.1:1337/contacts?id=中文"

the result:
                 widnows7                                                  
                            linux
ie9             browser:get the hello world 
page                                            browser:get nothing   
                 server print: 
/contacts?id=                                                     server 
print: nothing

firefox21.0  browser:get the hello world 
page                                             browser:get the hello 
world page
                 server print:/contacts?id=%E4%B8%AD%E6%96%87             
server print:/contacts

Correct use of HandleScope in an asynchronous node addon

Cecil Rock — 2013-05-23T02:44:44


I'm writing a asynchronous Node Addon, but I have been struggling to figure 
out if I need to use a HandleScope in the "After" function that calls the 
client JavaScript callback. I've seen examples showing with and without new 
scopes, but never any explanation why. Here is an example:

void asyncWorkAfter(uv_work_t* req) {
   HandleScope scope; // <-- Do you need a new scope?

   const int argc = 1;
   Local<Value> foo = String::New("foo");
   Local<Value> argv[] = { foo };

   // assume I got my callback function out of req
   callback->Call(Context::GetCurrent()->Global(), argc,  argv);

   callback.Dispose();

   // if i use a new HandleScope, what happens to argv when we go out of scope?
   // Do i need to do something like a scope.Close() to copy argv to the parent scope?}

Do you need/want a HandleScope when you call the callback?
What happens to argv in the example if you do use a new HandleScope?


Thanks for the help!

Cecil

RE: Re: Retrieving values asynchroniously

Peter Rust — 2013-05-23T13:24:41

categories?

 

The closest thing I know of is to work down NPM's "most depended on" list
(https://npmjs.org/browse/depended), for each package, you can look at the
description and keywords to get a sense of what the category it belongs in.

Re: Re: nodejs 0.10.x on yocto1.3

Erwin Schaefer — 2013-05-23T09:35:26

Hello, and thanks for your inputs.

I've tried to rise ulimit -s to the maximum possible (i.e. 16384 on my
Fedora 18 x86-64), but to no avail.
I guess openembedded (which runs on my Fedora 18) uses a reasonnable stack
size for building, if not the "ulimit -s" one (have to check). After all,
it is for this reason that we cross-compile!

When branch "master" of openembedded switched to yocto 1.3/gcc 4.7, a lot
of extra tune features began appearing in the compile lines (at least for
my target, the beaglebone). And since openssl seems to use more than 600
source files, I can understand that this may overflow the size of the
argument list...

Best regards,

Erwin




On Wed, May 22, 2013 at 8:04 PM, Ben Noordhuis <info-GlD9/+i8LImWrUy98/Atqw< at >public.gmane.org> wrote:

Re: Re: Run node.js on W2k?

Adam Reynolds — 2013-05-23T09:17:23

I have to say this post scares me a little. You are trying to get node
running on one very old OS with a huge security risk. It's not even funny.

You'd be better off taking the machine and putting Unbuntu on it or ANY
other current OS.




On Wed, May 22, 2013 at 9:19 PM, Bert Belder <bertbelder-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

Re: Re: trying to wrap my head around "promises" - async vs Q

Baz — 2013-05-23T07:29:45



I am new to Node and trying to decide between promises, asynch and vanilla, 
there are so many good arguments for each. Mikeal, do you mind expanding 
further how using promises in your own, non-shared, code could hinder use 
of node? Do a lot of the libs that depend on asynch require you to use 
asynch as well (or make things easier if you do)?

Best,
Baz


On Sunday, November 11, 2012 10:46:05 PM UTC-8, Mikeal Rogers wrote:

Re: Re: Retrieving values asynchroniously

Baz — 2013-05-23T06:24:02

I'm a node newb and I don't know enough to make my own judgments between
various (generally very professionally written) frameworks/libs. I rely on
the wisdom of the community and generally my first step in researching a
solution is to search github and order by most stars. I then google to be
sure or search the mailing list, which is how I got here. I want to find
and use tools that embody the spirit of Node, that most people use, that
stay as close to the metal as possible, and with minimum abstractions to
get what I need done. The answer I was unequivocally looking for is to use
asynch - regardless of whether it's the best or not.

I ended up reading a lot of Bruno's Ramblings (that's the name of his
blog), and a lot about streamline, and it's clear that Bruno's not only
hyper-intelligent but an excellent communicator. Streamline seems really
cool, but it's way more than an asynch tool, and an entire paradigm shift
on how to write node. One that would be irresponsible of me to take on
before learning the

Re: Run node.js on W2k?

Bert Belder — 2013-05-22T20:19:21


Windows XP SP3 and Windows Server 2003 are the oldest supported versions.

Re: I am finding it Hard to use node.js

Isaac Schlueter — 2013-05-22T19:25:29

Hi, Kaweesi.

Typically the way to run a node program is from your regular command
line interface.  (Either the bash shell in Unix systems, or the `cmd`
program on Windows.)

Write your javascript codes in a file called "server.js".  Then, on
the command line, cd into the folder containing that file, and type:

    node server.js

It sounds like your'e on Windows.  If so, then the program with the
Node icon is the "repl".  This stands for "Read Evaluate Print Loop".
In this program, you can type a few codes, and node will run it, and
print the results, and then prompt you to enter more codes.  You can
also get here by typing `node` on the regular command line without any
arguments.




On Wed, May 22, 2013 at 12:05 AM, Kaweesi Simon <kaweesimon-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote: