gmane.comp.lang.javascript.nodejs

Node v0.10.8 (Stable)

Isaac Schlueter — 2013-05-24T22:46:27

2013.05.24, Version 0.10.8 (Stable)

* v8: update to 3.14.5.9

* uv: upgrade to 0.10.8

* npm: Upgrade to 1.2.23

* http: remove bodyHead from 'upgrade' events (Nathan Zadoks)

* http: Return true on empty writes, not false (isaacs)

* http: save roundtrips, convert buffers to strings (Ben Noordhuis)

* configure: respect the --dest-os flag consistently (Nathan Rajlich)

* buffer: throw when writing beyond buffer (Trevor Norris)

* crypto: Clear error after DiffieHellman key errors (isaacs)

* string_bytes: strip padding from base64 strings (Trevor Norris)


Source Code: http://nodejs.org/dist/v0.10.8/node-v0.10.8.tar.gz

Macintosh Installer (Universal): http://nodejs.org/dist/v0.10.8/node-v0.10.8.pkg

Windows Installer: http://nodejs.org/dist/v0.10.8/node-v0.10.8-x86.msi

Windows x64 Installer: http://nodejs.org/dist/v0.10.8/x64/node-v0.10.8-x64.msi

Windows x64 Files: http://nodejs.org/dist/v0.10.8/x64/

Linux 32-bit Binary:
http://nodejs.org/dist/v0.10.8/node-v0.10.8-linux-x86.tar.gz

Linux 64-bit Binary:
http://nodejs.org/dist/v0.10.8/node-v0.10.8-linux-x64.tar.gz

Solaris 32-bit Binary:
http://nodejs.org/dist/v0.10.8/node-v0.10.8-sunos-x86.tar.gz

Solaris 64-bit Binary:
http://nodejs.org/dist/v0.10.8/node-v0.10.8-sunos-x64.tar.gz

Other release files: http://nodejs.org/dist/v0.10.8/

Website: http://nodejs.org/docs/v0.10.8/

Documentation: http://nodejs.org/docs/v0.10.8/api/

Shasums:

```
c1b81939e55d42fd7a90ec88ab23fd7a411ed77c  node-v0.10.8-darwin-x64.tar.gz
4474b8d4222efd6f6076243a4aa78e72760ee01a  node-v0.10.8-darwin-x86.tar.gz
898283b1ba8a9732c98ce38a89dc15af23291702  node-v0.10.8-linux-x64.tar.gz
2e15464289f618245fc6f420191490c144d81be3  node-v0.10.8-linux-x86.tar.gz
9a36b001ce5eef52641b836a42d1fc69c516d329  node-v0.10.8-sunos-x64.tar.gz
490d9a6d2a300fd2750a4a227288aed67a767713  node-v0.10.8-sunos-x86.tar.gz
96218cb0c14fbcaa76165fbe5a3af402883f898b  node-v0.10.8-x86.msi
a713f339195dd009d2614fac25b61bc88295f063  node-v0.10.8.pkg
d650a09ae868bb04f424e3560658c15b9a885b5b  node-v0.10.8.tar.gz
38034b7a6bca2dbe3aaacc3cc8aa9920394baaf7  node.exe
19cd4ae9f3edeaa259e5ca84abd28dea400a91d7  node.exp
1ccffaf0ff0f4bb11e8d23a2938366fd87b3e583  node.lib
079f617ef81507a6b5fe7e8bd1f5a2f109a574ec  node.pdb
985d55d1ba49f47354ba13a419d678bf73634ef9  x64/node-v0.10.8-x64.msi
25d4d74c73cd57346094979e5c51c5b16d6dcb83  x64/node.exe
19587e8301371e721695c7aed335f74c6873dfaf  x64/node.exp
4a002dd8a1742431fc99a2a92580a3040a796f2c  x64/node.lib
8d18200f9fe81805fe81201355d9f3509bd0c81b  x64/node.pdb
```

HTTP - how to send multiple pre-cached gzipped chunks?

Sławek Janecki — 2013-05-24T19:04:20


Lets say I have 2 individually gziped html chunks in memory. Can I send 
chunk1+chunk2 to HTTP client? Does any browser supports this? Or there is 
no way to do this and I have to gzip the whole stream not individual chunks?

I want to serve to clients for example chunk1+chunk2 and chunk2+chunk1 etc 
(different order) but I don't want to compress the whole page every time 
and I dont want to cache the whole page. I want to use precompressed cached 
chunks and send them.

nodejs code (node v0.10.7):

// creating pre cached data buffersvar zlib = require('zlib');var chunk1, chunk2;
zlib.gzip(new Buffer('test1'), function(err, data){
  chunk1 = data;});
zlib.gzip(new Buffer('test2'), function(err, data){
  chunk2 = data;});

var http = require('http');
http.createServer(function (req, res) {
      res.writeHead(200, {'Content-Type': 'text/plain', 'Content-Encoding': 'gzip'});
      // writing two pre gziped buffers
      res.write(chunk1); // if I send only this one everything is OK
      res.write(chunk2); // if I send two chunks Chrome trying to download file
      res.end();}).listen(8080);

When my example server returns this kind of response Chrome browser display 
download window (it doesnt understand it :/

Node JS and DOM Manipulation

Tamil selvan R.S — 2013-05-24T07:17:49

Hi,
 This is a post to get some suggestions over DOM Manipulation using JSDOM 
in nodejs. 
 We have currently written a service which crawls given url on the fly and 
input it to JSDOM to inspect DOM with jQuery.
 We see that this service consumes 90% of CPU [Expected]. The urls scraped 
are quite heavy in their html content and around ~100 req/sec
 As the task is quite CPU intensive [not really async aswell] we feel that 
when concurrency of requests increases our service goes unresponsive.
 Are we missing out something?

[ANN] vnc over gif

Andrey — 2013-05-24T10:09:50

https://github.com/sidorares/vnc-over-gif

Friday evening project: vnc viewer based on animated gif image stream. 
Browser requirement: netscape 2.0+

Regards
Andrey.

Non-web always-blocking cpu-intensive high-memory node worker

Baz — 2013-05-24T05:36:12

I'm new to node and I am investigating using node for a non-web
always-blocking cpu-intensive high-memory process. The process basically
runs in an infinitely loop, loading a lot of data from a datastore into
memory, applying complex (blocking) business logic, then saving the result
back to the store, and starting over again. It doesn't respond to
web-requests or process html or anything of that nature. It just needs to
run this loop.

Is this an acceptable use-case for node, given that it breaks every
rule-of-thumb ever written? Is node reasonably efficient at doing this (it
doesn't have to be the best solution in the world, just good enough)? Are
there pitfalls to consider with having an always blocked event loop? Are
there any issues with using lots of ram on a server (30gb+) in a single
node?

Additionally, anyone know of any good write-ups of people who have tried
this?

Thanks for listening!

Baz

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?id=%E4%B8%AD%E6%96%87
I search the google, someone says it's an msie bug, it does not encode the 
parameter.
But i don't know why it works on windows7 but not works on linux.

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

Run node.js on W2k?

Michael Hipp — 2013-05-22T17:27:03

Hello,

I'm totally new to node.js. Is there any way to get the Windows x86 version 
to run on w2k?

I'm attempting it with *v0.10.7* and it dies with "node.exe is not a valid 
Win32 application".

Thanks,
Michael

TCP Clients connections supported

Marco — 2013-05-22T16:21:35

Hi

Currently I'm developing a TCP server with nodejs client, clients are GPS 
devices that send data by GPRS_TCP.

How many clients could I connect to the server and it does not fail? The 
idea is that 100 devices to be sending data to the server very 30 seconds.

Best Regards

Marco

[ANNC] Announcing StrongLoop Node 1.0 GA, an enterprise-ready distro of Node.js.

Jimmy Guerrero — 2013-05-22T15:30:22

StrongLoop Node gives you a path forward to get technical support and
bug fix coverage before heading into production. For developers who
are new to Node, our distribution gives you the perfect starting
point. Navigating over 30,000 modules and the unique features of Node
itself can require a lot of mental overhead and be an overwhelming
experience. StrongLoop Node comes with vetted modules, advanced
features like message queue support, private NPM repos, and a utility
for scaffolding Node applications called slnode.

More details in the announcement blog:

http://blog.strongloop.com/announcing-strongloop-node-1-0-ga-an-enterprise-ready-node-js-distribution/

Jimmy Guerrero
Community
< at >strongloop

Crash when sending socket to child process

鋆邓 — 2013-05-22T05:49:27

I use the code from http://www.nodejs.org/api/child_process.html. The main 
process will quit when client sent any data to server. (It quited silently 
without any more log, so I think it crashed, is it?)
My operation system is Windows 7 x64. Tested both x86 version and x64 
version nodejs(0.10.7).

It runs very nice on another 2 computer(one Windows7 x64 and another 
Windows XP x86) and linux(ubuntu x64). I cannot find any difference between 
my computer and the other Windows7 x64. Any one met same problems?

main.js:

var normal = require('child_process').fork('worker.js', ['normal']);
var special = require('child_process').fork('worker.js', ['special']);

// Open up the server and send sockets to child
var server = require('net').createServer();
server.on('connection', function (socket) {

  // just the usual dudes
  normal.send('socket', socket);
});
server.listen(1337);

worker.js

console.log("Worker: ", process.pid, " started");
process.on('message', function(msg, client){
if (msg == "socket") {
console.log("Worker: ", process.pid, " got a client");
client.resume();
}
})

process.on('exit', function(){
console.log("Worker: ", process.pid, " over")
});

console:

C:\Test>node main.js
Worker:  5484  started
Worker:  1548  started
Worker:  5484  got a client

C:\Test>

Newbie question here

Toddy Mladenov — 2013-05-22T05:19:29

Just started looking as some node.js code that I inherited. It uses 
passport and express and I get the following error when I try to load the 
home page of the site:

Tue May 21 2013 22:12:38 GMT-0700 (PDT) 1
GET / controller: main action: index
<<< protect from forgery [0 ms]

/Users/toddysm/Development/Projects/iddioodev/app/controllers/application_controller.js:19
if (session.passport.user) {
           ^
TypeError: Cannot read property 'passport' of undefined
    at Object.loadUser 
(/Users/toddysm/Development/Projects/iddioodev/app/controllers/application_controller.js:19:13)
    at Object.<anonymous> 
(/Users/toddysm/Development/Projects/iddioodev/node_modules/railway/lib/controller.js:377:20)
    at 
/Users/toddysm/Development/Projects/iddioodev/node_modules/railway/lib/controller.js:354:24
    at process._tickCallback (node.js:415:13)

It seems the session object is not created but I have no idea why. 
Shouldn't this be created automatically when the user accesses the site?

Thanks for the help!
Toddy

I am finding it Hard to use node.js

Kaweesi Simon — 2013-05-22T07:05:54

I am very new to using Technologies like node.js. I have followed Tutorials 
but Every time i try to run the Script of the Server, i don't get any 
Reply. I installed Node.js and i have to commandline interfaces ie one 
having the Icon of Node.js and the Other is Like My Normal commandline. 
Which one should i use. How best can i configure node.js to Work with 
Localhost. My Goal of Using Node.js is to create a Real Time Notification 
System and interface it with my php site. Any Help Would Much be Appreciated

[ANN] node-ifttt-webhook - a Wordpress XML-RPC to webhook proxy server for ifttt

Ken — 2013-05-22T00:18:24

Nothing profound here, but might be of interest to the hardware hacker/home 
automation geeks in the crowd.  I've been playing around with internet 
connected devices a lot recently (it's actually my day job now<http://www.snupi.com/>) 
and so have been playing with the various channels available on IFTTT, aka 
IF This Then That (http://ifttt.com), which include some cool hardware like 
the Philips HUE bulbs and Belkin's WeMo stuff.  Ironically despite being 
very hacker friendly in conception IFTTT doesn't actually make it easy to 
invoke arbitrary code, but some clever folks had figured out how to hack in 
a webhook proxy in via the existing WordPress integration.  I've ported 
their PHP version to node and it is available here:

https://github.com/femto113/node-ifttt-webhook

Once running on a (public) server, this service allows you to activate the 
WordPress channel and then invoke almost any URL via a recipe.  Running in 
your DMZ you could then use it to hit stuff within your local network, 
which is essentially how I'm using it.  Feel free to try it out and post 
any issues on Github.

On a side note I find this kind of an interesting showcase for node, since 
the whole thing is only about 50 LOC (about 100 if you include the test 
case).  The test actually fires up it's own little http server to verify 
that the webhook is being called, I can't even really wrap my head around 
how I'd write that sort of test in another system.

--Ken

The Magnode content management system (and "Why Node.js?!")

Austin William Wright — 2013-05-21T18:29:59

Every so often (maybe twice a week in IRC) someone asks about a blog,
e-commerce, or content management system for Node.js. I feel compelled to
ask "Why Node.js", because it seems like one of those "I want to do it
because I can" rationales. Most people have that exact reason, and not much
else (that's not non-generic). But that's not to say no such reason exists.

I had this idea of mine long before Node.js, so I have what I believe are
more practical reasons. A CMS is I/O heavy, not especially computationally
heavy. ECMAScript is a natural choice because it's prototype-based,
event-oriented, and of course, the language of the Web. A little while
after having been introduced to Node.js, I realized what Node.js was
perfect for, and started work somewhere around v0.4.

Node.js (or any single-process paradigm) brings some design challenges. For
instance, in my application, I can't make the assumption that all
legitimate requests will only use a certain amount of memory — some
applications may require streaming an indefinite amount of data, for
instance. However, handling multiple requests per process means the total
resource usage of a single request can't be limited, at least by the OS.
The only solution I know of so far is, for every attacker, to make sure
that the non-generic attack of growing the process's memory to the point of
crashing is more expensive than a simple, generic DOS.

I also don't want to make any assumptions how the application might be
used, I can't assume that only Jade or MongoDB will be used, for instance
(even if they are natively supported).

Here's my implementation: Magnode.org <https://magnode.org/>. It's designed
as a framework, with a simple default application that tries to cover most
use cases. It uses many other libraries, particularly ones I had to write,
like rdf <https://github.com/Acubed/node-rdf>, jsonschema<https://github.com/Acubed/jsonschema>,
and contenttype <https://github.com/Acubed/contenttype>.

It works on the notion that a user requests a resource, the resource is
identified, then formatted into the requested Content-Type (via the Accept
header or the request URL), usually HTML or JSON, but depending on the
resource, you might also format e.g. a time series as an image, or a PDF
file. It's especially designed for graphs of data, like the Web (and
dereferencing nodes on it, hence the name Magnode).

It's pretty capable right now: You start it up, run through a quick
web-based installer to initialize the configuration, then you can log in
and see a front page of blog posts (reverse chronological order), create
new posts, pages, add items to menus, create new menus, create users, and
such. With some coding, it should be relatively simple to create a new type
of output, maybe you want to generate an image from data for instance, this
should be possible with a fairly short file, maybe 50 lines (it involves
simply registering a function with a domain of whatever data type you want
to process, and a range of Document and image/png, or whatever media types
the output would be).

While presently it only works with MongoDB, it's not designed for a
specific database (only about a dozen of 88 files are MongoDB-specific),
and I intend to support a number of data storage schemes. The next storage
scheme will be HTTP endpoints (effectively making Magnode an HTML frontend
to an HTTP API). Additionally I would like to see relational databases, an
IndexedDB-style database (where you query documents using specific indexes
instead of by their data), and an RDF graph database.

Here are some features that work right now:

- Make lists and tables of content. The front page, by default, is a
list of blog posts.
- Revisioning of content - documents are only inserted into the database
by default.
- Custom schemas and content types, and custom templates for formatting
them.
- Resources are first-class: Most everything is an HTTP resource,
including blog posts, users, the content-types themselves, and even server
configuration if so desired. This means a single code base for doing
everything related to changing configuration and editing content.
- Pluggable user authentication and authorization.
- Content-Type negotiation can return any number of content types with a
Content-Location header, XHTML and JSON are supported natively. It also
supports most of the HTTP headers like Etag, Accept, If-Match, and similar.
This means the server is naively a RESTful HTTP API.

Some use cases that I've designed for, but have yet to implement, are:

- A better UI for editing structured data and markup: Right now, many
operations like adjusting schema definitions requires editing raw JSON.
- Extensive caching of rendered resources. (Nonetheless, it still
performs faster and serves more requests than a comparable installation of
Drupal.)
- Straightforward editing of templates and themes, including compression
and aggregation of CSS and JS files.
- Self-registration and support for third party accounts (log in with
OpenID, etc).
- Content-Type aware formatting of error pages.
- User comments on resources
- OAuth (or similar) for delegating access of resources to third parties
(bearer tokens with sandbox permissions are already supported or easily
implemented).
- Editing and updating content in-line, and in real time (perhaps
integrate the MediaWiki VisualEditor<http://www.mediawiki.org/wiki/VisualEditor>).
Magnode can update resources with a standard HTML POST form, or a PUT
request with a JSON document, but maybe also PUT raw HTML of the edited
page, parsing the HTML back into a database record. This would mean editing
pages in-line with very little client-side scripting required, and no
significant requirement on the server either.
- Support more data sources as mentioned: relational (SQL), graph (RDF),
and resource (HTTP) databases.

One cool use case that I've already implemented is using Magnode as a
gateway that adds an HTML representation of resources to an otherwise JSON
HTTP API. With this, you can use your web browser as a console to interact
with the API endpoint.

I'd really appreciate any help that people can offer. If you have MongoDB
running, take five minutes and go to the "Get Started" page<https://magnode.org/download>,
then let me know what you think. The source is available through the
website or on GitHub <https://github.com/Acubed/magnode>. It is public
domain.

Austin Wright.

[ANN] Express Train - Lightweight MVC framework for Express

autoric — 2013-05-21T17:20:46

Hi All,

https://github.com/autoric/express-train 

Express Train is a lightweight mvc framework built on top of express. We 
have developed express train internally and been using it in our 
applications over the last year.

In comparison to other mvc frameworks express train aims to provide *consistent 
structure* and bootstrapping to your projects *without obscuring or or 
rewriting the express api*. 

With our 1.0 release we are now feeling like the project is pretty stable 
and ready to open up to a wider audience. If you have interest, please 
check it out and give feedback.

Thanks!

How to Firmly Establish your Reputation

Ray Connell — 2013-05-21T15:30:33

1. Publish your project idea to git. At this point it doesn't matter if it
works. Someone will immediately contribute it and fix up the bugs.
2. Make sure it has a fairly high revision level to start out. That way lots
of people will download it and you have the best chance of getting some
contributors.
3. Do as many of these projects as possible so people will know how creative
you are.
4. Finally, make sure your full name is on everything so the credit will go
where the credit is due.
Best of Luck in your new career.

how to Pass tls.CleartextStream instance to worker process

chenxu zhao — 2013-05-21T11:07:58

 i have the same problem like this post

http://stackoverflow.com/questions/12971738/pass-tls-cleartextstream-instance-to-worker-process

I want to use a stream.pipe to send.

but how, like this ?

var  tls_socket = new net.sockert()
cleartextStream.pipe(tls_socket);

but tls_socket can't send to child_process too .

child_process.js:134
      handle.onread = function() {};
                    ^
TypeError: Cannot set property 'onread' of null
    at ChildProcess.handleConversion.net.Socket.send
(child_process.js:134:21)
    at ChildProcess.target.send (child_process.js:436:52)
    at Server.<anonymous>
(/Users/zcx/BestApp/android-mqtt-push-server/server_master_zmq.js:171:12)
    at Server.EventEmitter.emit (events.js:98:17)
    at SecurePair.<anonymous> (tls.js:1117:16)
    at SecurePair.g (events.js:175:14)
    at SecurePair.EventEmitter.emit (events.js:92:17)
    at SecurePair.maybeInitFinished (tls.js:896:10)
    at CleartextStream.read [as _read] (tls.js:430:15)
    at CleartextStream.Readable.read (_stream_readable.js:294:10)

The debugger is not responding with a payload message when I send a V8 protocol command

Gabriel Petrovay — 2013-05-21T09:57:48

As I detailed in this issue: https://github.com/joyent/node/issues/5512

the V8 debugger does not respond with a body (or it hangs somewhere).

Any ideas why?

product roadmap?

Gowrishankar Holalkere — 2013-05-21T01:42:26

Has Joyent or node team announced their product roadmap? Is it something 
they have talked about at any forums? I think for many folks to consider 
using node, they would like to see the vision / strategy / roadmap for the 
product so that they can commit to it. Any info around this, please share.

Build Live Streaming Server with Nodejs

Duy Nguyen — 2013-05-21T08:45:38

Hi guys,

I have the plan to build a live streaming server using nodejs to support
multi-users connect to my site to watch short clips in real time.

I have googled but not get much valuable results.

Just want to show off our scenario:
   "each day server will show 1 video at the specific time, for example
14:00, userA connects to server at 14:00 and video is streamed to userA's
browser, 10 mins later userB connects to our server, then userB can see the
video from 10th min afterward, and so on...."

I need a solution for both backend (streaming server) and front end(video
player), anyone who which one supports and used widely?

Best all,