I wrote https://github.com/jesusabdullah/node-ecstatic for this kind of
stuff, there are a bunch of code samples and a bin script for quickly
serving static assets from a folder. Flatiron was using it when I worked at
Nodejitsu so it's fairly well-tested.
--Josh
On Thu, Mar 14, 2013 at 1:14 AM,
I am trying to install socket.io and I get this message
npm install socket.io
https://lh5.googleusercontent.com/-EMb8MP8FLgU/UUGlU_kIskI/BhE/KjQOZ3sIkCM/s1600/socket.png
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
meteor isn't node. it uses node as container, but introduces it's own
programming model and principles, own apis and even own package manager.
it's not helpful in the context of this topic.
surely one can find the meteor idea interesting and move to it, but then
it's another mindset, event
In my application i am using RedisStore for storing session. using below
code
app.use(express.session({ store: new RedisStore({host:'system ip address',
port:6379, prefix:'chs-sess'}), secret: 'lolcat', key : sid }));
but I can't understand below things
1. where this value stored(means
Hey,
ramesh laxmisetti laxmisettiram...@gmail.com writes:
In my application i am using RedisStore for storing session. using below
code
app.use(express.session({ store: new RedisStore({host:'system ip address',
port:6379, prefix:'chs-sess'}), secret: 'lolcat', key : sid }));
but I
Discussion here: https://github.com/joyent/node/issues/5005
If you've ever done something like:
fs.unlink(file); // don't care if it works or not
This won't work in v0.10.0 any more. If you want to ignore errors you need
to pass in an empty callback. Just wanted to post a heads-up here as
Just wanted to give out some thanks to all the core folks who landed
v0.10.0. My results using it so far are nothing short of awesome.
My app is using node.io, and gets clobbered constantly by problematic web
pages. Even monit and an internal kill timer could not keep it going.
I implemented
On Mar 14, 6:24 am, Bhushan N.N bhushan...@gmail.com wrote:
I am trying to install socket.io and I get this message
npm install socket.io
https://lh5.googleusercontent.com/-EMb8MP8FLgU/UUGlU_kIskI/Bh...
`npm install socket.io` should skip compilation for the ws module if
you do not
I am a newbie and just started of reading the *Node Up and Running *book
I am running *npm install socket.io* from command prompt. However, if I
ignore the error being displayed, the examples still seem to work.
Thank you
Bhushan
On Thursday, 14 March 2013 19:03:58 UTC+5:30, mscdex wrote:
On
On Thu, Mar 14, 2013 at 2:16 PM, Matt hel...@gmail.com wrote:
Discussion here: https://github.com/joyent/node/issues/5005
If you've ever done something like:
fs.unlink(file); // don't care if it works or not
This won't work in v0.10.0 any more. If you want to ignore errors you need
to
I still think the documentation should be updated to reflect that callbacks
are no longer optional. They are only optional if the call succeeds, which
you can't really know ahead of time.
On Thu, Mar 14, 2013 at 10:43 AM, Ben Noordhuis i...@bnoordhuis.nl wrote:
On Thu, Mar 14, 2013 at 2:16 PM,
Can't seem to click on the link (404ish style page saying missing or not
shared).
--
--
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
Ah, missed that - my bad :)
On Thu, Mar 14, 2013 at 11:01 AM, Ben Noordhuis i...@bnoordhuis.nl wrote:
On Thu, Mar 14, 2013 at 3:58 PM, Matt hel...@gmail.com wrote:
I still think the documentation should be updated to reflect that
callbacks
are no longer optional. They are only optional if
StreamWrap: Aborting due to unwrap failure at ../src/stream_wrap.cc:125
I'm seeing this error after upgrading to node v0.10. I haven't debugged
into it yet, but does anyone have any details about that error?
Thanks,
Chris
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
On Thu, Mar 14, 2013 at 4:10 PM, Chris Scribner scr...@gmail.com wrote:
StreamWrap: Aborting due to unwrap failure at ../src/stream_wrap.cc:125
I'm seeing this error after upgrading to node v0.10. I haven't debugged into
it yet, but does anyone have any details about that error?
Thanks,
Cool, thanks!
--
--
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@googlegroups.com
To
And jquery now uses use strict too!
AJ ONeal
(317) 426-6525
On Wed, Mar 13, 2013 at 4:49 PM, AJ ONeal coola...@gmail.com wrote:
FYI: grunt-init gruntplugin uses 'use strict'; for all grunt plugins. Yay!
That's what we need to see more of!
It would be nice if npm init would follow suit (or
On Wed, Mar 13, 2013 at 10:19 PM, AJ ONeal coola...@gmail.com wrote:
Rick:
I'm just thinking of the children here. I don't think you should have to
be an expert to be a beginner. I'm vehemently pro technology that gets us
closer to the goal of just being able to sit down and do stuff well.
Anyone?...
On 10 March 2013 22:01, Nick Middleweek n...@middleweek.co.uk wrote:
Hi,
I'm after a cloud provider for hosting NodeJS apps that supports CI,
perhaps in a similar way to CloudBees supports Java/ CI/ Git, etc. I'm not
claiming to be an expert with CloudBees, in fact I'm far from
On Thu, Mar 14, 2013 at 12:19 PM, AJ ONeal coola...@gmail.com wrote:
And jquery now uses use strict too!
Actually, we had to back that out.
https://github.com/jquery/jquery/commit/0e2977583c0455eda940a28b2499cad2cbf24ee4
http://bugs.jquery.com/ticket/13335
--
--
Job Board:
I couldn't view it because I don't want to sign up for google docs.
On Thu, Mar 14, 2013 at 8:02 AM, Bradley Meck bradley.m...@gmail.comwrote:
Can't seem to click on the link (404ish style page saying missing or not
shared).
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
I meant google+
On Thu, Mar 14, 2013 at 10:46 AM, Mark Hahn m...@hahnca.com wrote:
I couldn't view it because I don't want to sign up for google docs.
On Thu, Mar 14, 2013 at 8:02 AM, Bradley Meck bradley.m...@gmail.comwrote:
Can't seem to click on the link (404ish style page saying
On Thu, Mar 14, 2013 at 1:29 PM, Scott González scott.gonza...@gmail.comwrote:
On Thu, Mar 14, 2013 at 12:19 PM, AJ ONeal coola...@gmail.com wrote:
And jquery now uses use strict too!
Actually, we had to back that out.
Important to note that we are not happy about this at all.
Rick
Hi Michael! I've been working on a proof of concept, regarding minimal
clients for redis!
So far I've reached 56 LOC. Obviously this isn't for use in production :)
Thanks for your post, it gave me the final motivation for creating a public
repo.
Here's the code:
Just a proof of concept regarding the use of Proxy objects!
A minimal redis client:
https://github.com/eveiga/node-miniredis
Best regards,
Edgar Veiga
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You
This is super awesome.
Can some one please do some benchmarks.
On Thu, Mar 14, 2013 at 11:54 PM, Edgar Veiga edgarmve...@gmail.com wrote:
Just a proof of concept regarding the use of Proxy objects!
A minimal redis client:
I feel so great about the fact that node.js will never have something backed
out because it breaks asp.net ajax postbacks :)
-Mikeal
On Mar 14, 2013, at 11:09AM, Rick Waldron waldron.r...@gmail.com wrote:
On Thu, Mar 14, 2013 at 1:29 PM, Scott González scott.gonza...@gmail.com
wrote:
On Thu, Mar 14, 2013 at 2:56 PM, Mikeal Rogers mikeal.rog...@gmail.comwrote:
I feel so great about the fact that node.js will never have something
backed out because it breaks asp.net ajax postbacks :)
It's rage inducing.
Rick
-Mikeal
On Mar 14, 2013, at 11:09AM, Rick Waldron
Hey sorry for the delay.
I don't think Raft is at the stage when you would want to use it. The post
I made was really just to see what the community thought about the project.
There are no stable versions of raft. The most text/docs/info your going to
find about raft right now is this post.
Many functions in NodeJS have a Sync pendant to the non-blocking functions.
Why is there no blocking pendant in the child_process module?
I've giving up as I tried to iterate over a directory and call for every
file
child.exec
how should my app now, that every process completed his task?
I don't sure I understand your issue.
But there is an example that iterate over a directory, to run test files
https://github.com/laverdet/node-fibers/blob/master/test.js
On Thu, Mar 14, 2013 at 5:32 PM, Sebi sebastian.tild...@googlemail.comwrote:
Many functions in NodeJS have a Sync pendant
There are tons of modules to help with asynchronous code.
https://npmjs.org/package/async is pretty popular. If you end up in
callback hell, you're probably not designing your code properly. Take some
time to look at various modules and find one with a style that you like.
On Thu, Mar 14, 2013
I have been using https://github.com/arturadib/shelljs for my execSync needs.
Works quite well
for building command line application in node that doesn't require concurrency
;)
On Thursday, March 14, 2013 at 9:40 PM, Scott González wrote:
There are tons of modules to help with asynchronous
Okay, but I think there should be an execSync like they do it in almost
every other module.
My oppertunity is, that every developer should have the ability to choose
if he goes the async or syncronously way.
Regards,
Seb
Am Donnerstag, 14. März 2013 21:40:08 UTC+1 schrieb Scott González:
Thank you, I know that there is already a module called exec-sync.
I only posted that here, to inform the devlopers of nodejs, that it could
be useful to attach some function in nodejs, that does that synchronously.
Some function like this:
stdout = execSync('ls ./mypath');
Am Donnerstag, 14.
That's a great oppertunity? but it's not in line with the structure and goals
of node.js.
Node has synchronous file operations. The reason it has sync file operations is
that there are many cases where you actually **want** to stop the entire server
until you get back data from the filesystem
var filesInProgress = 0,
fancyCallback =
allDone = function(){ // boom}
files.forEach( function(filename){
filesInProgress++
exec('ls '+filename,function(err, stdout, stderr){
filesInProgress--;
//do something with it
if(filesInProgress === 0) allDone();
Callback hell is a place you decide to go on your own. I'm not following you
down there...
Here is an alternative example made in callback heaven, where we embrace
asyncronous control flow like our first-born:
var async = require('async-array').async
var fs= require('fs')
var
But, what should you do if you can't serve anything after all sub-processes
have completed where work?
Am Donnerstag, 14. März 2013 22:02:11 UTC+1 schrieb Mikeal Rogers:
That's a great oppertunity? but it's not in line with the structure and
goals of node.js.
Node has synchronous file
But, what should you do if you can't serve anything after all sub-processes
have completed their work?
Am Donnerstag, 14. März 2013 22:02:11 UTC+1 schrieb Mikeal Rogers:
That's a great oppertunity? but it's not in line with the structure and
goals of node.js.
Node has synchronous file
I think you meant to say you can't serve anything *until* a sub-process has
completed its work
I've been using Node for CLI scripting, and a synchronous exec would be nice to
have just like the synchronous file IO is nice to have.
-- Dick
On Mar 14, 2013, at 2:22 PM, Sebi
Sorry, yes I've meant *until*.
Yes that's the second thing in CLI scripting. It's hard to write CLI
Applications if you have only the async option. I know it, because I've
tried to write a readline-application and the sync apps looking cleaner for
me.
I think I'm not the only person, who must
https://github.com/joyent/node/issues/1167 - stdio options need to be
specced out still.
--
--
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
OMG, so old and nobody has done something yet.
Am Donnerstag, 14. März 2013 22:48:46 UTC+1 schrieb Bradley Meck:
https://github.com/joyent/node/issues/1167 - stdio options need to be
specced out still.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
I downgraded because of other issues, but it would be nice to get
confirmation that it's not just me :/
--
--
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
On 03/14/2013 11:02 PM, Mikeal Rogers wrote:
That's a great oppertunity? but it's not in line with the
structure and goals of node.js.
Node has synchronous file operations. The reason it has sync file
operations is that there are many cases where you actually **want**
to stop the entire
Callbacks are easy (*). Sync calls are an abomination in node.js.
Unfortunately we cannot get rid of the ones that are already there. But we
should not add more.
(*) Some claim that they are easy for us humans. I find them too painful
for humans but still easy because they can be mechanically
Hope that no process completes before fileInProgress is set to two!
Race-Conditions...
Am Donnerstag, 14. März 2013 22:05:10 UTC+1 schrieb greelgorke:
var filesInProgress = 0,
fancyCallback =
allDone = function(){ // boom}
files.forEach( function(filename){
filesInProgress++
Most real world use cases for this are not for performance, they are for
shelling out to utilities, the alternatives are hideous as we found in nsh
: https://github.com/AvianFlu/nsh/wiki/nsh
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
now I'm getting it with the old version so something else must be going on.
On Thursday, March 14, 2013 3:06:29 PM UTC-7, anywho wrote:
I downgraded because of other issues, but it would be nice to get
confirmation that it's not just me :/
--
--
Job Board: http://jobs.nodejs.org/
Posting
Patch welcome.
https://github.com/joyent/node/issues/1167
On Thu, Mar 14, 2013 at 3:33 PM, Bradley Meck bradley.m...@gmail.com wrote:
Most real world use cases for this are not for performance, they are for
shelling out to utilities, the alternatives are hideous as we found in nsh :
;) That's a clever use of Proxy!
If you want to get *ultra* tiny, check out Pieter Noordhuis' own node
client that is tucked away in the node-hiredis repo:
https://github.com/pietern/hiredis-node/blob/master/hiredis.js
Anyway, pretty awesome what you can do with a simple protocol and some
That Proxy API is dead, very soon it will be replaced by the direct Proxy
spec.
Rick
On Thursday, March 14, 2013, Michael Jackson wrote:
;) That's a clever use of Proxy!
If you want to get *ultra* tiny, check out Pieter Noordhuis' own node
client that is tucked away in the node-hiredis
53 matches
Mail list logo
