BrowserQuest/server at master · mozilla/BrowserQuest. Introduction to npm. Static Version.
Google's v8 is pretty nice, but its documentation is rather spotty. We figured we'd share bits of knowledge we used. Thanks go to to the v8-users discussion group for inspiration. There will likely be two kinds of articles: example articles and discussion articles.
Algorithm. Frameworks. Screencasts. Mastering Node - Open Source Nodejs eBook. Node.js Knockout. Mongoose « Gradebook. Add Update: Mongoose 1.0 has been released, and we recommend going to our dedicated website for the most up-to-date information and code At LearnBoost, we like to consider ourselves hackers. We look to implement the best technical solutions for our needs then tell people how we did it and hope they fork our code, contribute and make it even better. To make a kick-ass solution for schools , we needed a data store that was scalable, fast and able to keep up with constant iterations of features.
The talk ran through why node.js is useful for realtime web apps, how to get it and ... I gave a talk on November 25, 2010, on Node.js, and related technologies, to the Vancouver Drupal Users Group. The talk ran through why node.js is useful for realtime web apps, how to get it and Express up and running, and how to access data from Drupal and MongoDB.
Statistics Views Total Views Views on SlideShare Embed Views Actions Likes Downloads 9 Embeds 248 More... Usage Rights © All Rights Reserved. Node.js: uses and ideas? Pixel Ping: A node.js Stats Tracker. Since the day we launched, ProPublica has encouraged people to republish our stories for free.
We even license our stories under Creative Commons (CC). However, in the past we've had trouble knowing precisely which stories had been republished where, and we had no way of knowing how many people were reading our stories on sites that republished them under our CC license. Shortly after the redesign of our site, we started working on a system that would help us solve this problem.
When we found out that Jeremy Ashkenas, a developer at DocumentCloud, was working on a similar problem, we joined forces, and finished work on a lightweight stats tracker, which we are open sourcing today. I pushed 20 more of my projects to GitHub. Remember my previous article "I pushed 30 of my projects to GitHub?
" Well, I just gathered 20 more projects that I had done (or did recently) and pushed them all to GitHub. Quick note on GitHub - GitHub is the best invention ever for programmers. Nothing stimulates you more than pushing more and more projects to GitHub and seeing people forking them, following them, finding and fixing bugs for you. I wouldn't be doing so much coding if there wasn't GitHub. If you like my projects, I'd love if you followed me on github! Right, so here are the new projects: How To Node - NodeJS. Parsing file uploads at 500 mb/s with node.js » Debuggable Ltd. A few weeks ago I set out to create a new multipart/form-data parser for node.js.
We need this parser for the new version of transloadit that we have been working on since our setback last month. The result is a new library called formidable, which, on a high level, makes receiving file uploads with node.js as easy as: var formidable = require('formidable') , http = require('http') , sys = require('sys'); Essentially this works similar to other platforms where file uploads are saved to disk before your script is invoked with a path to the uploaded file. What's nice about this however, is that you can hook into the whole thing on a lower level: We use that interface for processing HTML5 multi-file uploads as they come in, rather than waiting for the entire upload to finish.
This makes certain functionality extremely difficult to support.