00:00 <ceej> hey, is there a simple way to override a specific find_by method, like find_by_login ?

00:00 <maxogden> markq: line 80

00:00 <guy> https://gist.github.com/76eb6e8bfe3908020c9c

00:00 <guy> any clue?

00:00 <Lingerance> ceej: obj.find_by_object = function() { ... }

00:01 <markq> that...sucks

00:01 <ceej> Lingerance: so you can't do it inside class Account < ActiveRecord::Base ?

00:01 <Lingerance> ... are you in the right channel?

00:02 <ceej> o wups LOL

00:02 <ceej> ty :)

00:02 <maxogden> rad

00:02 <Lingerance> np

00:02 <guy> Just in case, I've installed nodejs using this repo http://nodejs.tchol.org/

00:03 <maxogden> guy: git clone https://github.com/joyent/node && cd node && git checkout v0.6.7 && ./configure && make && sudo make install

00:03 <guy> What's wrong with the repo?

00:03 <Draggor> isn't latest version 0.6.8?

00:04 <maxogden> guy: just giving you alternatives that i know work

00:06 <guy> ok.. that's really strange

00:06 <guy> https://gist.github.com/9ac97182736b4a0ae177

00:06 <guy> nodejs is under `nodejs` name rather than `node`?

00:07 <maxogden> guy: im guessing the weird repo you're using does that

00:07 <guy> It is official repo fromhttp://nodejs.org/

00:08 <maxogden> guy: it says at the bottom "This project is not formally related to or endorsed by the official Joyent Node.js open source or commerical project."

00:08 <maxogden> guy: i am just being pedantic though

00:09 <maxogden> guy: you should rename it to node cause everything will expect the binary to be node and not nodejs

00:09 <guy> is there a way to rename it?

00:09 <maxogden> guy: mv /usr/bin/nodejs /usr/bin/node probably

00:10 <guy> merci!

00:17 <Lingerance> guy: Fedora has a package named node that is in /usr/bin/node; I would recomend you not do the mv command

00:18 <guy> I am using CentOS 6

00:18 <Lingerance> Instead: ln -s `which nodejs` ~/bin/node

00:18 <Lingerance> There's a good chance it has the same package...

00:19 <mateodelnorte> Anybody ever had an "Error: EMFILE, Too many open files" error with bouncy?

00:19 <maxogden> mateodelnorte: 3 days ago i heard substack say he has never used bouncy in production so i'm sure he'd love a bug report

00:20 <mateodelnorte> maxogden: heh. well, sounds like an indicator I should use HAProxy in prod... :P thx

00:21 <maxogden> mateodelnorte: node is more like LAProxy

00:21 <ChrisPartridge> mateodelnorte: sounds like max file descriptors was hit

00:22 <mateodelnorte> ChrisPartridge, I think that's it. But the question is why. My proxy app dies, but my clustered, child_process spawned child sites don't. Indicates to me it's inside bouncy.

00:23 <ChrisPartridge> mateodelnorte: bouncy just isnt handling the error

00:23 <guy> ok. I messed up a bit. Anyone mind helping me around? How to remove node.js after installing it using `git clone https://github.com/joyent/node && cd node && git checkout v0.6.7 && ./configure && make && sudo make install`

00:24 <guy> I've tried `make uninstall` and it says success, but `node -v` still brings v0.6.8

00:25 <ChrisPartridge> mateodelnorte: https://github.com/isaacs/node-graceful-fs - might be able to just drop that in

00:25 <maxogden> guy: if you installed 0.6.7 and it says 0.6.8 then it must be hitting a different installation, no?

00:26 <guy> no, I've installed 0.6.8; sorry wrong copy paste

00:26 <guy> but only v changes.

00:26 <bradleymeck> mateodelnorte, thats a leaking file descriptor then

00:26 <maxogden> guy: gotcha

00:28 <bradleymeck> mateodelnorte, we saw something similar in node-fork recently

00:28 <mateodelnorte> so far all of these scenarios sound like issues bouncy should handle internally, no?

00:28 <bradleymeck> mateodelnorte, correct, bother substack

00:28 <mateodelnorte> Will do. Thanks guys

00:28 <bradleymeck> or try node-http-proxy

00:29 <maxogden> guy: this is all make uninstall does: https://github.com/joyent/node/blob/master/tools/installer.js#L114-117

00:29 <guy> -bash: cd: /usr/bin/node: Not a directory

00:30 <guy> but I can still access node in CLI

00:30 <maxogden> guy: `which node`

00:30 <guy> /usr/bin/node

00:30 <guy> ....

00:30 <Aria> ... Right. It's not a directory ;-)

00:30 <maxogden> guy: haha

00:30 <guy> oh wait. -bash: cd: /usr/bin/node: Not a directory

00:30 <guy> yeah, didn't notice "Not a directory"

00:31 <superjoe> wow

00:31 <superjoe> guy, time to take a 15 minute break? :)

00:31 <guy> Not really.. I made changes on production server that result in failure. 5:31

00:32 <guy> Hopefully no one is awake yet.

00:32 <superjoe> you made the changes directly on the server?

00:32 <guy> Don't really understand why make uninstall didn't work.

00:32 <guy> Moving project files to new server, superjoe.

00:33 <guy> https://gist.github.com/38da92e2b89fef577d96

00:33 <guy> It didn't actually do https://github.com/joyent/node/blob/master/tools/installer.js#L114-117

00:34 <guy> any clue why?

00:41 <guy> anyway.. removed everything manually

00:50 <guy> after I install forever using `npm install forever -g`

00:50 <guy> and type `forever` afterwards, I get -bash: forever: command not found

00:51 <maxogden> guy: it sounds like your path is wonky

00:51 <maxogden> guy: in general

00:51 <guy> anyone can help me out sorting this all out?

00:51 <guy> I am starting to freak out a bit..

00:51 <konobi> guy: `hash -r`

00:52 <guy> no output

00:52 <konobi> ...

00:52 <Aria> no output is unix for "That went splendidly."

00:53 <guy> yeah, but `forever` still doesn't work

00:53 <guy> this is output of `npm list`

00:53 <guy> https://gist.github.com/6e28e33da62568aead70

00:53 <guy> so it is installed

00:58 <bradleymeck> guy is /var/www/virtualhosts/dev.anuary.com/node on your PATH env variable? and that /bin etc?

00:59 <bradleymeck> but yes your PATH is pretty toasted, i would check `env` and try to fix it

01:02 <Aria> npm list -g would show yout globally installed

01:25 <yogieric> When I did "npm search jsdoc", I see lots of options. What's best?

02:08 <shanebo> hey guys what's fastest way to output a buffer in answering a request?

02:09 <maxogden> .toString() ?

02:09 <DeezGz> res(buffer)

02:10 <segv> hey with http.request can I receive streaming json from cli, (want this all local to the app not client side)

02:10 <shanebo> DeezGz do you mean res.end(buffer)?

02:10 <DeezGz> sorry fs.createReadStream(f).pipe(res)

02:10 <DeezGz> sorry fs.createReadStream(buffer).pipe(res)

02:10 <shanebo> DeezGz and will that end on it's own when it's done?

02:11 <segv> I don't want to receive just the "end" data does res.on('data', ...) stream is what I should have asked

02:11 <maxogden> segv: this should get you going https://gist.github.com/1609973

02:11 <DeezGz> i dont remember

02:11 <segv> maxogden: ah

02:11 <maxogden> yes streams emit end

02:11 <SubStack> segv: .pipe(request(...), { end : false })

02:11 <maxogden> unless you do o/

02:11 <segv> cool

02:12 <segv> Minsunderstood what I was doing, I post, and the data is streamed back have a "msg" field I wanted to stream back straigt but that couchdb example looks promising

02:12 <SubStack> maxogden: \o teamwork

02:12 <SubStack> ^5

02:12 <segv> indeed thanks

02:12 <* maxogden> touches substack's hand

02:12 <shanebo> thanks DeezGz, I'll give it a go

02:12 <DeezGz> no brob

02:13 <DeezGz> thank you

02:14 <maxogden> stackhaus residents should receive kickbacks from any node conference budget surplus

02:14 <DeezGz> politics

02:15 <SubStack> stackhaus === helping

02:15 <maxogden> anyone know if express supports .pipe(response) yet

02:16 <segv> SubStack: so that .pipe(request()) is attached to the data event?

02:17 <maxogden> segv: if you have streaming json coming in you'll want to use a streaming json parser such as JSONStream

02:17 <maxogden> segv: and that will give you a thing you can .pipe() to a request

02:17 <segv> got it

02:18 <markq> is cluster used for scaling node?

02:21 <wingie> is there a good node.js library that generates 40 chars SHA-1 keys?

02:26 <wingie> require('crypto').createHash('sha1').digest('hex')

02:35 <shanebo> DeezGz can't get it to work...

02:36 <DeezGz> u talking about the piping

02:37 <shanebo> DeezGz yeah

02:37 <DeezGz> let me find something

02:41 <maxogden> shanebo: are you using express

02:41 <DeezGz> is this a string buffer or a raw buffer

02:41 <shanebo> raw buffer

02:41 <DeezGz> for file

02:41 <shanebo> maxogden, no

02:41 <DeezGz> are you spitting back to a http?

02:41 <DeezGz> or to where?

02:42 <shanebo> yes

02:42 <DeezGz> try buffer.pipe(where u want it to go);

02:42 <shanebo> currently i'm just using response.end(buffer)

02:43 <shanebo> but I tried your example of:

02:43 <shanebo> fs.createReadStream(buffer).pipe(response)

02:43 <shanebo> and each file throws a 500

02:44 <DeezGz> try buffer.pipe(response) see if that works

02:45 <maxogden> shanebo: you might find the filed module useful if you are dealing with files

02:45 <DeezGz> check this out see if this helps

02:45 <DeezGz> http://elegantcode.com/2011/04/06/taking-baby-steps-with-node-js-pumping-data-between-streams/

02:46 <DeezGz> old school shoud work

02:46 <maxogden> shanebo: also there is lotsa code in here that does piping to http responses https://github.com/maxogden/rewriter

02:46 <DeezGz> util.pump(buffer, response);

02:48 <shanebo> DeezGz, no dice on buffer.pipe(response)

02:49 <shanebo> gonna try the util example

02:49 <DeezGz> that one should work, that how i started with this stream stuff, still wrapping my head around it myself

02:52 <shanebo> DeezGz still throwing a 500

02:54 <maxogden> shanebo: are you rolling your own server using the http module?

02:54 <maxogden> shanebo: and where does the buffer come from?

02:54 <shanebo> SubStack, what's the best stream alternative to response.end(buffer)?

02:55 <SubStack> shanebo: what are you doing?

02:55 <SubStack> that question doesn't make sense

02:55 <SubStack> but you probably want .pipe()

02:55 <SubStack> code would help

02:55 <DeezGz> ok looking

02:56 <DeezGz> are you writing your headers first

02:56 <DeezGz> mime type & length

02:56 <shanebo> SubStack I've read response.end(buffer) isn't as good as piping. However, I'm unclear how to pipe a buffer.

02:56 <shanebo> yes headers are all set

02:57 <SubStack> shanebo: if you paste some actual code it would clear up a lot of the confusion

02:58 <shanebo> SubStack I have a buffer of a file cached and when it's route is matched I write it's headers and response.end(asset.body) (asset.body is a buffer)

02:59 <shanebo> ˆˆ and all that works

02:59 <shanebo> SubStack I'm trying to implement a pipe alternative (if it's better practice)

03:00 <SubStack> shanebo: that doesn't help. code would make sense

03:00 <DeezGz> ok try var tmp_buff = ''; buffer.on('data',function(chunk){tmp_buff += chunk;});buffer.on('end',function(){res.write(tmp_buff);res.end();})

03:00 <SubStack> DeezGz: buffers do not work that way

03:01 <DeezGz> what version of node are you on

03:01 <shanebo> SubStack what code do you need to see? My response.writeHead code and response.end is all there is here.

03:02 <SubStack> shanebo: it's very hard to reason about code without being able to see it

03:02 <maxogden> i can reason about code without being able to see it

03:02 <maxogden> plus open source is for hippies

03:03 <maxogden> i want to keep my intellectual property thank you

03:03 <* SubStack> uses government mind rays to steal maxogden's intellects

03:03 <DeezGz> so you want to spit a bufferd file to a response

03:04 <DeezGz> are their any real experts that can help this man with his problems

03:04 <shanebo> SubStack http://cl.ly/0p0p2z3x2k1a1p3U1X2F

03:04 <[AD]Turbo> hi there

03:05 <SubStack> shanebo: why not just app.use(express.static(__dirname + '/static')) ?

03:05 <SubStack> or use ecstatic

03:06 <DeezGz> so asset.body is a buffer?

03:06 <SubStack> or some other module

03:06 <SubStack> that is for serving static files

03:06 <shanebo> DeezGz yes

03:06 <DeezGz> ok

03:07 <shanebo> SubStack because I'm writing my own framework to try an learn things

03:07 <DeezGz> fs.createReadStream(asset.body).pipe(response); take off the response.end bit

03:07 <DeezGz> me too, dont give up all new to me

03:07 <shanebo> DeezGz already tried that, it doesn't work

03:08 <SubStack> fs.createReadStream(filename).pipe(res) you mean

03:08 <SubStack> why do you want to keep file contents in memory?

03:08 <SubStack> also this: https://github.com/mikeal/filed

03:08 <DeezGz> no respone in you cause

03:08 <shanebo> SubStack because I assume it's faster?

03:09 <SubStack> does that actually matter?

03:09 <shanebo> of course

03:10 <DeezGz> what version of node are you using

03:11 <shanebo> v0.6.7

03:11 <DeezGz> ok

03:12 <DeezGz> console.log(asset.body.pipe) tell me if u can see anything in your console?

03:13 <DeezGz> i want to see if it has a pipe method

03:15 <DeezGz> this is me pipe function if this helps u

03:15 <DeezGz> Pipe = {

03:15 <DeezGz> init:function(S,o){this[S](o)},

03:15 <DeezGz> R:function(o){

03:15 <DeezGz> fs.createReadStream(o.s,o.o).pipe(o.d);

03:15 <DeezGz> },

03:15 <DeezGz> W:function(o){

03:15 <DeezGz> o.s.pipe(fs.createWriteStream(o.d,o.o));

03:15 <DeezGz> }

03:16 <DeezGz> R = readStream W = Write stream

03:16 <DeezGz> Pipe('W',{s:'your source',o:'stream option'})

03:17 <DeezGz> Pipe('R',{s:'your source',o:'stream option'})

03:17 <timoxley> SubStack the id given to the connection on server and the id given to the client connection… should they be the same?

03:17 <timoxley> SubStack RE dnode

03:18 <DeezGz> sorry wrong way

03:18 <DeezGz> like this

03:18 <DeezGz> Pipe.init('W',{s:req,d:'test.json',o:{bufferSize:(7*1024)}});

03:19 <segv> maxogden: tis may be my issue, http.request doesn't support streaming? I'm going about this all wrong and reading mixed tuts/outdated ones, etc.

03:19 <DeezGz> Pipe.init(Mode, object{s:'source',d:'destination',o:'options'})

03:23 <SubStack> timoxley: nope

03:23 <timoxley> SubStack great. thanks.

03:23 <robzdc> any nodejs/socket.io tut with all functions and that?

03:24 <maxogden> segv: it does

03:24 <segv> maxogden: Okay, so I'm just overcomplicating this haha

03:24 <maxogden> segv: see this readme for example https://github.com/mikeal/filed

03:25 <segv> maxogden: ah, all i'm trying to do is pass a stream back to terminal

03:25 <segv> not serve it to a client

03:26 <DeezGz> o ok

03:26 <maxogden> .pipe(process.stdout)

03:26 <timoxley> robzdc look at the examples and the test cases on the socketio githubs.

03:26 <SubStack> .pipe(process.stdout, { end : false }) probably since closing stdout is probably not what you want

03:26 <SubStack> can get annoying for debugging when stdout gets closed >_<

03:26 <segv> That would be placed on the req?

03:27 <* segv> tests

03:27 <maxogden> segv: it would be placed on whatever stream you want to stream back to terminal

03:27 <segv> k

03:27 <maxogden> segv: can you describe what you're trying to do again? accept json and modify it in some way and stream it back to stdout?

03:29 <maxogden> SubStack: http://felixge.s3.amazonaws.com/11/nodejs-streams.pdf

03:31 <segv> maxogden: have a remote api, almost similar to the twitter stream, I post to it and it sends back information, a section of it i oull out and parse

03:31 <maxogden> segv: do you pull out the parse this section before the 'sends back information' step happens?

03:32 <segv> maxogden: No sending back information, I was trying to parse it on the end

03:32 <maxogden> segv: hah im confused

03:34 <segv> maxogden: I'm half asleep trying to figure this out haha

03:34 <DeezGz> wake up

03:34 <segv> trying :(

03:34 <DeezGz> eastcoast or west

03:49 <martin_sunset> Hi guys, any recommendations for a bootstrap compatible form builder that works on client and node?

04:02 <wingie> anyone here using flatiron?

04:18 <booyaa> wingie: no one awake in #nodejitsu?

04:19 <DeezGz> hellp

04:29 <robzdc> How do you send a message to a specific socket? can you? or you have to do a broadcast and then specify wich user is gonna see the message?

04:30 <SubStack> net.createServer(function (c) { c.write('beep boop\r\n') })

04:30 <SubStack> is how

04:34 <vnjs> @sub

04:55 <hemanth> I have a simple function defined in a js, have a package.json for the same, build and link works, even require work also, but not able to access any of the functions in it! As in the object thus created has no property at all, I'm missing something for sure, but don't know what

04:56 <maritz> hemanth: can you give us a gist?

04:56 <hemanth> maritz, ok, one second

04:56 <maritz> i expect you've set whatever functions you want to export in the exports variable?! :)

04:56 <hemanth> o ya!

04:57 <hemanth> this is first ever npm package :)

04:57 <maritz> nice :)

04:57 <hemanth> could be npm package

04:57 <hemanth> just a simple function to return http response text for a given code

04:57 <maritz> be sure to read the npm help pages for developers, json and packages :)

04:58 <hemanth> something like that is there already i presume https://github.com/joyent/node/blob/master/lib/http.js

04:58 <maritz> hemanth: apparently, yes. :D

04:59 <maritz> didn't even know that :)

04:59 <hemanth> it was not there few days back

04:59 <hemanth> :(

05:00 <maritz> hemanth: are you sure? most of these are still from the very beginning of node in july 09.

05:00 <hemanth> or I must have missed it

05:00 <maritz> happens :)

05:01 <hemanth> :) So getting response text is very much possible with http right?

05:10 <maritz> hemanth: require('http').STATUS_CODES

05:11 <* hemanth> does an rm -rf on his npm dir

05:11 <hemanth> :/

05:15 <hemanth> marienz, summarizing it all, npm init, npm build, npm link, npm install, npm publish . [ not to forget module.exports ]

05:15 <hemanth> right?

05:16 <hemanth> maritz, ^ oops

05:17 <sunglepuss> If I use snappy to compress on the server, how do I uncompress at the client?

05:22 <maritz> hemanth: depends on your package. i've never needed build for example.

05:22 <maritz> but if you have a build process, yeah

05:23 <hemanth> :) ok; now brain storming to come up with a better npm, heh eh

05:23 <maritz> wait, no. you shouldn't call npm build according to the man page

05:23 <maritz> what's wrong with npm?

05:24 <hemanth> heh heh i meant a better package from myside

05:24 <hemanth> npm is brilliant!

05:27 <hemanth> maybe some hardware interaction

05:31 <Nirav> help please i have custom server on that i have install node.js as well as npm but it doest allow me to set host and port to my application consol.log(app.address()); print null

05:32 <garrensmith> Nirav: console.log

05:33 <Nirav> yeh

05:33 <Nirav> but its print null only

05:34 <timoxley> SubStack so, if I want to fire ordinary events over socketio, does any dnode functionality expose socketio to allow that?

05:37 <SubStack> no

05:37 <SubStack> timoxley: do this instead: http://substack.net/posts/9bac3e

05:38 <timoxley> SubStack ok, that's what I thought.

05:38 <timoxley> cool

06:08 <* booyaa> ponders using minify/uglify to troll

06:08 <booyaa> yeah here run this code...

06:09 <booyaa> *blort*

06:12 <booyaa> hronous nature to hell!

06:12 <booyaa> eh?

06:17 <eldios> guys does anyone of you have a *GOOD* waterproof laptop backpack?

06:17 <eldios> I'm considering one from swissgear but I cannot understand if they are actually waterproof or not :/

06:18 <icebox> eldios: northsails - model surge?

06:18 <eldios> thanks icebox will check immediately

06:20 <eldios> icebox, does not look like t's waterproof

06:21 <icebox> eldios: I have been checking... and it seems your right.. well they don't state it is not waterproof :)

06:21 <eldios> that's a bit risky

06:22 <RLa> i haven never seen waterproof backpacks

06:22 <eldios> but in that case I would go for a swissgear

06:22 <eldios> http://www.swissgear.eu/the-ibex#1

06:22 <eldios> this one possibly

06:24 <icebox> eldios: cool

06:24 <RLa> i would expect waterproof backpack keep its contents dry when you submerge it into water

06:24 <eldios> yep

06:24 <eldios> RLa, yes that's why most of the time they say "water resistant"

06:25 <RLa> if you need real waterproof, get such laptop

06:26 <RLa> i think there are some that tolerate submerging into water

06:27 <icebox> eldios: and changing approach? a good backpack with a laptop waterproof skin?

06:28 <eldios> mm

06:29 <eldios> well tbh I do not need to submerge my laptop in water.. it's only that I do not it to get wet when I ride my motorbike and I'm surprised by rain

06:29 <icebox> eldios: ok... use two plastic bags :)

06:30 <eldios> that's a good workaround.. but if a good water resistant backpack existed I would have choosen that.

06:30 <eldios> anyway as I can read the one I was choosing from swissgear looks well water-resistant

06:31 <eldios> I'll buy that one and let you know =)

06:35 <eldios> well.. I was wrong.. an actual waterproof backpack exists --> http://www.amazon.com/Lowepro-DryZone-Camera-Backpack-Yellow/dp/B00009R855/ref=sr_1_fkmr0_2?ie=UTF8&qid=1327664079&sr=8-2-fkmr0

06:35 <eldios> works even against submersion XD

06:38 <prettyrobots> Where do people get textures for their CSS?

06:40 <sriley> what kind of textures?

06:40 <prettyrobots> Everyone is using nice subtle textures.

06:40 <prettyrobots> http://get.gaug.es/documentation/reference-listing/sharing/

06:40 <prettyrobots> Like in the blue bar there.

06:40 <prettyrobots> Or the background here:

06:40 <prettyrobots> http://dimsumthinking.com/2012/01/21/a-writers-eula/

06:40 <sriley> people usually work from a design thats made in a graphics application

06:41 <prettyrobots> Yup.

06:41 <sriley> in photoshop for example the subtle text is just a noise filter

06:41 <jacobrask> prettyrobots: you're looking for subtle patterns? try http://subtlepatterns.com :P

06:41 <prettyrobots> Yes! Thanks!

06:42 <prettyrobots> I'd just seen this, but I couldn't find it again.

07:02 <`10> https://github.com/ksdlck/sleepy.node

07:07 <timoxley> prettyrobots also http://www.minimal-patterns.com/

07:08 <prettyrobots> timoxley: Very cool.

07:08 <prettyrobots> Thanks everyone.

07:12 <Nirav> hi guys my node application running on 0.0.0.0 : 13886 but i can not open from brower its on live server

07:20 <RLa> Nirav, maybe firewall blocks it

07:21 <Nirav> Rla : have you any idea how can i prevent this problem

07:35 <rdmoshpit> hey all, I'm totally new to nodejs, and kind of newbie of programming...

07:35 <rdmoshpit> there is something I don't understand with my REST client

07:35 <rdmoshpit> I'm using restler

07:36 <rdmoshpit> when i make a get on google.com, it works fine

07:36 <RLa> i got disconnected

07:37 <RLa> Nirav, can you connect from the machine itself

07:38 <Yester> can please someone tell me if it's possible to do login sessions with nodejs and maybe a good module? i don't get a solution... i tried https://github.com/marak/session.js but i don't work for me :( maybe because i want to combine it with websockets

07:39 <rdmoshpit> damned, my problem is with prestashop api… can't login to the api :(

07:55 <timoxley> If i'm contracting to (not employed by) a company, and I figure we could solve their problems by building a bunch of modules, if they go open source, who should own the github repository?

07:56 <mansoor> timoxley, if it was done on their dime I think it should go to them because they own the rights to it

07:56 <ckknight> timoxley: it depends on where the copyright lies, which depends on the contract you're working under. If it's open-source, then it could be under their github repo and you could just clone it.

07:56 <mansoor> but I guess you could ask them, I dont' think they

07:56 <timoxley> my opinion is that it should partially depend on whose initiative it was to build the module

07:56 <mansoor> would mind you working on it

07:57 <mansoor> a "module" is just a piece of code you wrote for money :p

07:57 <mansoor> no different than any other line of code you write

07:57 <augustl> agree with ckknight, copyright is what matters

07:58 <timoxley> I see it that they are paying for me not for my code.

07:58 <augustl> doesn't matter how you see it, what matters is who holds the copyright :)

07:58 <prettyrobots> timoxley: What does the contract say?

07:58 <timoxley> well, actually currently we have no contract

07:58 <timoxley> it's pending.

07:59 <mansoor> lol from contractor to contractor bad idea :p

07:59 <timoxley> I have done work with them for the past 6 months, they are trustworthy

07:59 <mansoor> opens a big ugly can of worms

07:59 <prettyrobots> timoxley: Have you seen this?

07:59 <prettyrobots> http://vimeo.com/22053820?utm_source=swissmiss

07:59 <timoxley> no

07:59 <prettyrobots> Great talk.

08:00 <timoxley> I'm not at any risk of not being paid.

08:00 <prettyrobots> About contracts and payment in creative.

08:00 <timoxley> ok

08:00 <prettyrobots> Okay, but it sounds like you're confused about who holds the copyright on your work, so you should get that sorted out.

08:01 <prettyrobots> My understanding, IANAL, is that unless you have a contract that explicitly transfers copyright, then it says with you.

08:01 <prettyrobots> s/says/stays/

08:02 <augustl> timoxley: it makes sense that you discuss it with the client - your argument is valid. As in, you agree that they only buy your time, and the right to use what you produce, and they don't buy the copyright to it

08:02 <augustl> or at least some parts of what you produce, such as reusable decoupled standalone modules

08:02 <timoxley> augustl agreed.

08:02 <augustl> photographers do this I think. If you want to buy exclusive rights to a photo, the price quadruples

08:03 <timoxley> augustl agreed.

08:03 <augustl> the artifacts of photos and code is different though

08:03 <timoxley> augustl what do you mean

08:04 <timoxley> prettyrobots thanks, this is a good talk.

08:05 <augustl> timoxley: basically, a photo and code is not the same thing ;)

08:05 <augustl> so it's just an example of the pricing model, not an argument for using the pricing model for code

08:06 <PaulIIIIIIII> http://www.hot.ee/keber/pilt.JPG

08:07 <prettyrobots> http://24ways.org/2008/contract-killer

08:07 <prettyrobots> timoxley: http://mylawyergabe.com/

08:09 <timoxley> prettyrobots thanks

08:09 <timoxley> yeah i think I just need to talk to them about a new contract.

08:10 <timoxley> owning the code is so much more valuable to me (code is my business) than it is to them (business is their business)

08:14 <augustl> timoxley: I think the biggest challenge is to argue that doing so doesn't cause them to indirectly pay for the work you do other clients

08:14 <timoxley> sure

08:14 <timoxley> they were planning on releasing this stuff open source anyway

08:14 <timoxley> so i think they've got pretty good attitude

08:15 <timoxley> and theya re my only client at the moment

08:18 <khinester> hello

08:19 <richardrflores> khinester: hello

08:20 <richardrflores> khinester: Im just checking things out...using the webchat client.

08:21 <khinester> i am trying to build node 0.6.8 on freebsd but get an error https://github.com/joyent/node/issues/2623

08:23 <blup> could anyone recommend reading material for js security? id like to test my app..

08:26 <claudio> blup, I can suggest taking a look at fusker https://github.com/wearefractal/fusker

08:29 <blup> thanks claudio

08:39 <timmorgan> I was under the impression that Node.js has a 64-bit binary for Windows, but when I install and run on my Windows 64-bit machine, it's 32-bit.

08:40 <Glenjamin> mmalecki: you about?

08:40 <timmorgan> Is there a way to get a x64 binary of Node.js on Windows?

08:41 <timmorgan> I will accept a lmgtfy link :-)

08:43 <thomaschaaf> Hey what is the best XML parser for nodejs? (needs to be windows compatible)

08:45 <augustl> timmorgan: compiling it yourself, I guess

08:46 <timmorgan> bummer

08:48 <augustl> compiling node is really easy (on *nix at least)

08:58 <sparcd> anyone got any examples of how to make an ajax call inside node.js?

08:59 <tuhoojabotti> wut

09:00 <tuhoojabotti> sparcd: normal http get/post

09:00 <sparcd> yeah

09:00 <tuhoojabotti> consult the apt

09:00 <sparcd> found something here http://nodejs.org/docs/latest/api/http.html#http.get

09:00 <tuhoojabotti> api

09:00 <tuhoojabotti> that

09:01 <tuhoojabotti> res.on data

09:01 <tuhoojabotti> res.in end done

09:01 <tuhoojabotti> on*

09:01 <tuhoojabotti> sorry for mobile typos. :e

09:13 <RLa> damn internet today

09:16 <bluepaint> [Question:] I just installed vows on windows, but when I try "vows mytest.js" in cmd.exe, it isn't recognized as an external or internal command. (nodejs, npm, etc, Does work, however)

09:17 <peterrs> in node_modules i have a directory called sky with symlinks to some libraries inside my application.. like sky/router -> require("sky/router/file") is it possible to have npm build these symlinks when the package is installed, or do i have to add a scripts to "scripts" directory in package.json?

09:17 <timoxley> sparcd what are you truing to do

09:18 <timoxley> peterrs you might want to look into a private npm repo

09:18 <bluepaint> timoxley: can you help me too?

09:18 <bluepaint> [Question:] I just installed vows on windows, but when I try "vows mytest.js" in cmd.exe, it isn't recognized as an external or internal command. (nodejs, npm, etc, Does work, however)

09:18 <bluepaint> where can I find this vows file manually?

09:19 <timoxley> bluepaint npm install -g vows

09:19 <bluepaint> already done it. twice.

09:19 <bluepaint> hm.. with the -g

09:19 <rdmoshpit> wow, I have a strange behavior with the restler module and the authentification by username...

09:19 <timoxley> bluepaint -g will install it so it's available as an executable on your PATH

09:19 <peterrs> timoxley: ahh.. maybe i should explained myself better.. i pull my private repo from github.. run npm link.. and it basically just downloads the required packages needed to run the app, kinda like a tiny boostrap. but that is probably not what you meant?

09:20 <bluepaint> timoxley: aha. alright. it works now. thanks ALOT! :D

09:20 <timoxley> peterrs no, more like https://github.com/dominictarr/shadow-npm

09:20 <timoxley> bluepaint np

09:20 <timoxley> peterrs you could commit the modules into git

09:21 <timoxley> peterrs git add node_modules

09:21 <timoxley> peterrs if you dont' want to do that, you can set up a postinstall script that will be run by npm after install, perhaps you could put that stuff in there

09:22 <timoxley> peterrs npm help scripts

09:23 <timoxley> peterrs I'd put all the login in a a Make file, then invoke it via npm

09:23 <peterrs> timoxley: nah.. the shadow idea is good, but cannot publis the code to it though.. think i'll just to put this into my makefile :)

09:23 <timoxley> peterrs why can't publish the code to it? company secrets?

09:23 <peterrs> mm

09:23 <timoxley> mm

09:23 <peterrs> hail the corporates

09:24 <peterrs> guess i'll just have to wait until someone decides to create an easy way of hosting private repos on your own build server or something like that :)

09:25 <timoxley> peterrs you can run your own private npm https://github.com/isaacs/npmjs.org

09:25 <timoxley> I havent' done it but I know that's how the big guys do it

09:26 <peterrs> timoxley: yeah, i know.. but you know.. you never find the time to do just that.. maybe in the future! +1 github integration

09:27 <peterrs> thank you for the advice though :)

09:27 <timoxley> peterrs np

09:33 <markprovan> yo all

09:34 <jmar777> yo

09:35 <jmar777> in both node v0.6.7 and v0.6.8, my express application ALWAYS throws an ETIMEDOUT exception at exactly 1m15s after starting it

09:36 <jmar777> the stack trace isn't very long, but it's coming from net.js. I removed any code that involved connecting to databases, etc., so given that it's a connection issue, it must have to do with the http server itself

09:36 <jmar777> anyone else seen this?

09:38 <timoxley> jmar777 post some code

09:39 <jmar777> timoxley: will do. need to reduce it first. just realized i forgot to remove a module that's connecting to rabbitmq, so that's probably my prime suspect now

09:40 <timoxley> jmar777 hopefully the act of reducing it to the minimum required code to cause the bug will flush out the bug

09:40 <jmar777> timoxley: ya. digging around the net.js where the error was being thrown, it has to do with a socket connection

09:41 <jmar777> timoxley: so, the rabbitmq connection seems most likely (checking to see if rabbitmq is actually running now, it's on ec2). thanks!

09:42 <timoxley> jmar777 np

09:42 <RLa> anyone written service that employs data sync between multiple parties?

09:42 <jmar777> ya, that was definitely it. just ran for 3m35s before i killed it myself.

09:42 <jmar777> RLa: sortta, but we basically just piggy-backed on couchdb

09:44 <RLa> jmar777, we have relational data, which is actually quite flat, i would like to sync 1-2 tables, tables can be synced separatedly

09:44 <RLa> just haven't gotten how exactly to do it

09:44 <martinkr> i published a package to npm and my .npmignore included ".*" as a rule, but dotfiles in subdirectories still end up on npm. how do i exclude them?

09:45 <RLa> and without permanently storing delete events

09:45 <timoxley> RLa I'm building just that right now

09:45 <RLa> want to do some coop?

09:45 <timoxley> RLa for sure.

09:46 <RLa> can i pm?

09:46 <timoxley> sure

09:47 <CIA-101> node: 03Fedor Indutny 07master * r85a86b5 10/ tools/wafadmin/Tools/node_addon.py : waf: predict target arch for OSX - http://git.io/8CveZg

10:01 <thomaschaaf> Does anyone know an XML Parser which can run on windows?

10:01 <icebox> thomaschaaf: xml2js

10:02 <icebox> thomaschaaf: yes, it runs on windows

10:02 <neebz> Hello, I have created an expressjs app which is working fine. Now I need to create another app which uses some classes from the first app. e.g. I want to use the business logic layer from the first app. Is it possible?

10:02 <thomaschaaf> icebox: thanks let me look into that

10:03 <icebox> thomaschaaf: https://github.com/Leonidas-from-XIV/node-xml2js

10:03 <HardFu> neebz: sure

10:03 <HardFu> neebz: just load modules from the first app

10:03 <HardFu> those that you need

10:05 <neebz> HardFu: thanks. would still require to copy the files..no?

10:06 <neebz> HardFu: both apps aren't running on the same server. I was thinking along the lines of using git submodules?

10:06 <HardFu> ah yes if they don't run on the same server then yes, any way of sharing/copying files is ok

10:10 <senorpedro> hi

10:14 <markq> anyone know if cluster is the way to scale node?

10:14 <RLa> depends where bottleneck is

10:15 <RLa> if it's somewhere else, adding more instances will do nothing

10:15 <markq> suppose I'm getting 1000 requests per second on one process or something

10:15 <markq> how do I scale out

10:15 <markq> 10,000*

10:16 <icebox> markq: well... it depends on the kind of app... the number of requests doesn't mean too much

10:16 <RLa> if you have multiple cores, then yes, using cluster will help with computing power

10:16 <RLa> unless io becomes bottleneck

10:16 <jstash> markq: hypothetically speaking? yeah, cluster is one way to do it

10:16 <markq> a blog app for example

10:16 <markq> yea hypothetically

10:17 <markq> how do I scale node to different servers though?

10:17 <deedubs> markq: same as any other web tech, a load balancer

10:18 <markq> like HAProxy? or is there a module for node?

10:18 <jstash> HAProxy works

10:18 <markq> anything better?

10:19 <deedubs> if your on ec2 you can use their load balancer

10:19 <jstash> we just switched from nginx to HAProxy and are looking at Mongrel2 (but M2 is quite a different beast)

10:19 <markq> I'm on rackspace

10:19 <markq> so their load balancer would work for this case?

10:19 <deedubs> yes of course

10:20 <markq> and I just run the node app on a different server on the same port?

10:20 <markq> or is it more complicated

10:21 <markq> or just a different server*

10:21 <markq> how do I set it up?

10:21 <yawNO> woah

10:21 <yawNO> felt the earthquake

10:21 <yawNO> =\

10:21 <sriley> do you need to? you have enough traffic to need load balancing?

10:22 <sriley> otherwise youre just adding complexity to something thats not needed

10:22 <markq> I'm just thinking ahead

10:22 <markq> right now I don't need it

10:22 <deedubs> markq: don't do that

10:22 <sriley> look in to how to scale your application if and when it takes off

10:23 <markq> it's sort of a nightmarish situation if I can't handle the load and I'm trying to scale at that moment

10:23 <markq> is there a guide I can look at that anyone knows of?

10:23 <deedubs> if you want to think ahead build blog -> get famous -> host huge event get paid $millions -> go to vegas -> lose everything -> move into box on corner

10:23 <deedubs> so just skip everything and go live in a box

10:24 <markq> that's harsh lol

10:24 <markq> and it's not a blog

10:24 <markq> I was just thinking hypothetically

10:25 <sriley> whats wrong with your current technology stack with just add another box and load balance it? or upgrade to a larger dedicated server instead of virtual server (the easier option)

10:25 <bradleymeck> markq there is no easy book to read, a lot of network engineers do that full time if it is big enough

10:26 <thinkjson> What is the preferred method of connecting to Redis from Node.js? node_redis appears to have been removed from the npm registry...

10:27 <jstash> https://github.com/mranney/node_redis ?

10:27 <thinkjson> yeah

10:27 <joshsmith> markq: if you haven't heard the phrase YAGNI, now's the time to learn it

10:27 <thinkjson> it's not in npm anymore

10:27 <joshsmith> it's good to think ahead, but not if it stops you from getting traction now

10:28 <jstash> thinkjson: i'm interested in the same answer

10:28 <joshsmith> markq: go benchmark your app with ab and see how it performs

10:30 <CIA-101> libuv: 03Bert Belder 07v0.6 * rf925275 10/ test/test-fs.c : Fix windows build - http://git.io/j3LpzQ

10:31 <timoxley> markq dont' use ab, it is balls, use apache jmeter

10:32 <CIA-101> libuv: 03Bert Belder 07mcast-win * r7bc6f3a 10/ src/win/udp.c :

10:32 <CIA-101> libuv: Implement udp multicast methods on windows.

10:32 <CIA-101> libuv: Test is failing.

10:32 <CIA-101> libuv: uv_udp_set_membership is not supported for UDP/IPv6 sockets yet. - http://git.io/1wzxpg

10:32 <timoxley> thinkjson npm install redis worked for me

10:32 <markq> what's the best way to bench it then

10:33 <timoxley> jmeter is pretty damn good for benching.

10:34 <joshsmith> hmm I need to try out jmeter tim_smart

10:34 <joshsmith> errr, timoxley

10:35 <timoxley> joshsmith gives you lots of good stats as well as ability to ramp up/down traffic

10:35 <timoxley> joshsmith the interface sucks though. bit of a learning curve.

10:35 <joshsmith> ah that sucks

10:35 <joshsmith> I love how simple ab's interface is

10:35 <timoxley> still good though.

10:36 <joshsmith> I'll have to try it out at some point here

10:36 <joshsmith> I'm not worried enough yet. when I have to start thinking about earned media I'll deal with that stuff

10:36 <timoxley> ab doesn't model traffic remotely realistically, which is the problem. You can end up solving issues that you'll never ever have

10:37 <joshsmith> it did help point out some flaws pretty quickly, though

10:38 <timoxley> if you like ab, also check out siege

10:38 <joshsmith> yeah, I need to check that out, too

10:38 <thinkjson> timoxley: hmm. wonder why it doesn't show up in search.npmjs.org...

10:45 <thinkjson> my npm was jacked up because I installed 0.6 over 0.4

10:46 <Kingdutch> Argh, 'this' is biting me in the arse..

10:48 <Kingdutch> Actually, it's not, but my node app does get ridiculously slow when I send it input very fast :o

10:51 <bradleymeck> Kingdutch, if you are coercing buffers to strings a lot or doing CPU intensive processing that can happen

10:51 <Kingdutch> I don't know, I'm doing some IRC in/out

10:52 <Kingdutch> It should handle like 20 messages within a few seconds though, imo

10:52 <Kingdutch> bradleymeck: ^

10:56 <bradleymeck> Kingdutch, yep it should

10:56 <Kingdutch> So then it must be my code : |

10:57 <Kingdutch> Or the server was lagging, could be it too

11:03 <Kingdutch> bradleymeck: It's quite fast if I just send it one command, then it goes really slow if I put like 5-10 within a second

11:04 <gsmcwhirter> Kingdutch: are you doing sync operations or something?

11:05 <Kingdutch> gsmcwhirter: Somehow it looks like I'm very much doing sync operations, my debug output is totally synched =|

11:05 <gsmcwhirter> a gist or equivalent would possibly help us help you identify the source of the slowness

11:06 <gsmcwhirter> Kingdutch: ^

11:06 <Kingdutch> Hold on, it's quite a bunch

11:08 <Kingdutch> gsmcwhirter: I can give you the entire 250 lines, or strip it out to the init and onMessage function which should be enough I think (As that's what's slow, if you can help me async that I can do the rest myself)

11:08 <gsmcwhirter> Kingdutch: well, we can start there =) might be a problem elsewhere though

11:08 <gsmcwhirter> but that is the most likely place

11:09 <Kingdutch> Hold on

11:09 <Kingdutch> How can I async this:

11:09 <Kingdutch> this.onMessage( msg ); this.emit( 'data', chunk );

11:09 <Kingdutch> this.emit feels fine IMO (default EventEmitter thingy)

11:10 <Kingdutch> It's the onMessage within a loop that's blocking (The loop just reads out buffers and chops it into lines which is relatively fast)

11:10 <gsmcwhirter> I can't really tell from just that

11:10 <Kingdutch> I suppose I could do: var self = this; process.nextTick(function () { self.onMessage( msg ); }); but wont that ruin 'this' in .onMessage

11:10 <Kingdutch> hmm ok

11:10 <Kingdutch> hold on

11:13 <Kingdutch> gsmcwhirter: https://gist.github.com/2b736e115226f4425b88 <-- Tried to remove as much unrelated stuff as possible and added a few comments to potential bottlenecks

11:13 <Kingdutch> Program startup is a call to initialise() then connect()

11:14 <Kingdutch> When a message comes in the onData is called as a callback from the connection (net module), the onData adds the data to the buffer and just loops through it till a line is found (\r\n) and cuts that out

11:15 <Kingdutch> It then hands that over the parse to create a msg object, passing that to the onMessage callback which will distribute it depending on the type of message (In the case of the test this was a PRIVMSG with a command starting with the this.command character)

11:15 <Kingdutch> All the command does is a raw send on the bot

11:18 <gsmcwhirter> Kingdutch: the fishiest thing I see is that while loop. so when a chunk comes in, you append it to the buffer, but then you force it to handle all of it before you read the next chunk

11:19 <Kingdutch> Right, although that while in itself doesn't do a lot, so imo that's no biggy

11:19 <Kingdutch> It's the .parse and .onMessage which will add a lot of function calls, so would a process.nextTick help there?

11:20 <gsmcwhirter> possibly. I am not sure that is the best way to accomplish what you want, but it may work

11:21 <gsmcwhirter> and to answer a question from earlier, sending function (){ self.onMessage(blah);} shouldn't mess up the "this" referent for .onMessage

11:21 <gsmcwhirter> *sending = setting to nextTick

11:21 <Kingdutch> ok : )

11:22 <Kingdutch> What would you recon is the best way btw

11:22 <gsmcwhirter> I also don't know if how I would do it is the best way, but let me sketch something

11:26 <dob> which ide are u using to develop node applications? I know the last time i had a eclipse plugin with node startbutton, but can't find that anymore. Cloud9 can't install ace...

11:26 <dob> Is there anything else?

11:26 <tjfontaine> vim++

11:26 <dob> tjfontaine: Hope you are kidding :)

11:27 <tjfontaine> not in the least

11:28 <* Draggor> seconds the vim-nod

11:29 <gsmcwhirter> Kingdutch: https://gist.github.com/1689622 is my sketch (NB - probably quite buggy, seeing as it is a sketch)

11:29 <gsmcwhirter> for instance, probably forgot "var self = this;" in several places

11:30 <dob> no, i really hate the vim syntax... Is there not a real ide with debugger and breakpoints etc...

11:31 <Draggor> isn't that what node-inspector is for?

11:31 <gsmcwhirter> Kingdutch: also, like I said, not sure if that is the right way either

11:31 <Kingdutch> this.queue.push.apply(this.queue, lines); vs this.queue.push(lines) why?

11:31 <Kingdutch> And there's the problem of incomplete lines in the buffer = |

11:34 <dob> is node.js 64bit only?

11:34 <dob> on macosx?

11:35 <FnuGk> why would you run it in 32bit?

11:35 <Kingdutch> gsmcwhirter: A .emit is async right?

11:36 <dob> My current macbook is in service, so I had to use my 32 bit macbook pro :(

11:37 <gsmcwhirter> Kingdutch: not 100% sure, but I think it fires its stuff on the next tick

11:38 <gsmcwhirter> Kingdutch: I have to run, sorry to cut out before this is fully straightened out. good luck

11:38 <Kingdutch> Haha no problem, thanks for hte help : )

11:38 <FnuGk> i think all intel macbooks are able to run 64bit. It might just not be activated if your os is older than (snow) leopard

11:39 <timoxley> whoa, I'm having trouble with some basic stuff here.

11:39 <timoxley> module.exports = SomeConstructorFunction

11:40 <timoxley> if I do this, but set the prototype on SomeConstuctorFunction

11:40 <timoxley> every instance will get the same prototype

11:41 <timoxley> what's the best way to get a freshly generated prototype every time

11:41 <dob> FnuGK: No it's the first Macbook Pro from 2006 and there is only a coredou not a core2duo processor. So only 32bit

11:41 <timoxley> while still exposing constructor as module.exports and instantiating via new

11:43 <Kingdutch> Does anyone know if emit is always async?

11:44 <bnoordhuis> Kingdutch: emit as in EventEmitter.emit? it's never async

11:45 <FnuGk> dob: hmm what if you compile it yourself? Would that not result in 32bit bins?

11:45 <jerrysv> you can defer it

11:45 <dob> FnuGK: I am not sure... did not try it yet.

11:46 <thewildpendulum> anyone use mongoose?

11:46 <dob> I hate it to install a new computer lol

11:46 <FnuGk> thats life :)

11:46 <timoxley> bnoordhuis when you emit, it doesn't fire the listeners syncronously though… it will fire them on nextTick won't it

11:46 <timoxley> ?

11:47 <timoxley> thewildpendulum don't ask to ask, just ask

11:47 <bnoordhuis> timoxley: no

11:47 <timoxley> bnoordhuis whoa.

11:47 <bnoordhuis> timoxley: but (nearly) all the core code wraps the emit in process.nextTick

11:48 <timoxley> I thought that was part of the whole 'event driven' architecture

11:48 <timoxley> I should be doing that, I had jsut assumed it did it automatically

11:48 <timoxley> bnoordhuis mind blown.

11:49 <timoxley> bnoordhuis hm, I think it does what i described in actionscript, perhaps that's why I'm confused.

11:53 <thewildpendulum> i'm trying to store backbones models using mongoose and all the code i've read so far isn't very straightforward about how this actually done. is it as simple as opening a connection and calling save() or do i need to define a sync method?

11:57 <Kingdutch> bnoordhuis: Aaah really?

11:57 <Kingdutch> bnoordhuis: And yes as in eventemitter.emit

11:58 <bnoordhuis> Kingdutch: yep

11:59 <Kingdutch> bnoordhuis: Well that explains why everything runs so slowly.. trying to use .emit to get stuff async

12:00 <* Lingerance> wonders why emit doesn't default to making each call happen on the next tick

12:00 <jerrysv> Kingdutch: there are a couple of libraries that help you out a little bit, like eventreactor -- a thin wrapper that extends eventemitter with common patterns

12:00 <Kingdutch> Hmm ok

12:00 <Kingdutch> Is there a way to profile my node.js program to see where it spends its time? I feel like I'm just blindly adding overhead in an attempt to make it async and faster =|

12:00 <jerrysv> Kingdutch: see https://github.com/observing/eventreactor

12:00 <Kingdutch> Because if I give it more than 5 msgs at a time it'll die on me

12:01 <linac> if a connection is closed, all event listener on it would be removed automaticly?

12:03 <linac> i am worried about memory leak.

12:07 <timoxley> linac you can always remove them yourself with obj.removeAllListeners()

12:08 <timoxley> linac and you can see how many listeners there are with obj.listeners.length

12:09 <timoxley> linac where obj is an event emitter (in your case it might be a connection object)

12:10 <linac> so i have to add cleanup function listening on 'close' 'error' event for everywhere i use listener?

12:11 <linac> it's not a perfect design.

12:11 <timoxley> linac I avoid a lot of problems by using emitter.once

12:11 <timoxley> removes the listener automatically after firing once

12:12 <bnoordhuis> linac: not removing your listener doesn't inherently leak

12:12 <linac> event emitter should be able to automatic remove listener on event that would never be fired .

12:13 <timoxley> linac how can it now it would never be fired.

12:13 <timoxley> know*

12:14 <linac> for example, when connection is closed, 'data' event would never be fired.

12:14 <deedubs> linac: not true there could still be some data to be drained

12:15 <CIA-101> libuv: 03Bert Belder 07stat-regress * rcf8038e 10/ (src/win/fs.c test/test-fs.c test/test-list.h): Windows: fix stat("c:\\") regression - http://git.io/Dv_JVA

12:15 <linac> connection know whether there have data to drained. if no, listener could be removed safetly.

12:16 <timoxley> linac are you experiencing a leak/

12:16 <timoxley> linac it's quite possible that node is cleaning stuff up for you. Do a test.

12:16 <bnoordhuis> timoxley: he left :/

12:17 <timoxley> ah well.

12:19 <linac> timoxley, no now. but i think dangling listener would be a source to leak.

12:19 <bnoordhuis> linac: no

12:20 <bnoordhuis> i think you need to read up on how garbage collectors work...

12:20 <bnoordhuis> it's possible to leak but it takes more than a unused event listener

12:25 <linac> bnoordhuis, so closed connection and dangling listener are cicle-referenced, and garbage collector would work on them?

12:26 <bnoordhuis> linac: v8's garbage collector is smart enough to deal with circular references

12:43 <broofa> SubStack: Any idea why a PNG won't display on browserling's version of IE7, but displays on several virtualised IE7s I'm running elsewhere? E.g. /msg SubStack Any chance you might know why browserling.com

12:43 <broofa> (they have the exact same useragent, btw.)

12:44 <broofa> e.g. http://koivi.com/ie-png-transparency/test.png

12:45 <Phoenixz> Just to be sure, does node.js (or better, javascript) work with referenced objects? so if I have user={'name' : 'foo'}; a={'user' : user}; b={'user' : user}; a.user.name='bar'; console.log(b.user.name); I will get as a result "bar" ?

13:00 <augustl> are there any alternatives to jsdom that also works on windows?

13:02 <strager> augustl: The browser.

13:03 <stagas> augustl: htmlparser

13:04 <augustl> strager: you don't say :)

13:04 <stagas> augustl: and soupselect for a css selector

13:04 <augustl> stagas: tnx

13:04 <waxjar> is there an equivalent of Ruby's Bundler for node.js that deals exclusively with dependencies (opposed to the package.json)?

13:05 <gsmcwhirter> waxjar: why not use the package.json and npm?

13:05 <waxjar> i don't really need to keep track of a name and version and all that extra jazz

13:06 <gsmcwhirter> well, the version string is pretty loose...

13:06 <gsmcwhirter> could probably do ">= 0.0" or something

13:06 <isaacs> waxjar: so just name it whatever.

13:06 <isaacs> and give the version 1.1.1 or something

13:07 <augustl> one of the great benefits of Bundler is package.json. I hope something like that comes to npm soon

13:07 <augustl> it locks versions not just for your direct dependencies but for the full tree

13:07 <isaacs> augustl: just check them into git

13:07 <augustl> isaacs: never :P

13:07 <isaacs> that'll lock down not just the dependencies, but every line.

13:07 <isaacs> augustl: i don't get that.

13:07 <isaacs> why not?

13:08 <augustl> isaacs: makes the repo huge after some time

13:08 <isaacs> augustl: it makes the repo huge? really?

13:08 <isaacs> what are you depending on, cloud9?

13:08 <waxjar> i don't mean the version of my dependencies, but of my own project, if that makes sense

13:08 <waxjar> *versions

13:08 <isaacs> waxjar: yeah, just throw anything in there.

13:08 <isaacs> waxjar: if you're not publishign it, it doesn't matter.

13:09 <isaacs> waxjar: ther's an outstanding feature request to make name/version optional for non-published packages, but.. meh.

13:09 <waxjar> i guess, it'll do. it isn't pretty, though :p

13:09 <isaacs> it adds some complexity in a bunch of places, for really very little gain.

13:09 <augustl> isaacs: it also makes git do the job of the package manager

13:09 <isaacs> waxjar: you may come to find that having a version is kind of nice :)

13:09 <isaacs> augustl: no, it makes git do the job of the content tracker and lock-down-er

13:09 <isaacs> augustl: which is git's job.

13:09 <isaacs> augustl: i'm not suggesting you use git to find and manage deps.

13:10 <augustl> isaacs: I also think it only makes sense for that very repo. Say I put all the dependencies in my git repo, that doesn't help when people use npm to install my project as a dependency.

13:10 <isaacs> augustl: don't do that for things that get installed as a dependency.

13:10 <augustl> should my package embed all the packages it is using?

13:10 <isaacs> do that for deployable apps.

13:10 <isaacs> a website that you're pushing to a server, or a standalone application that does some stuff.

13:11 <augustl> isaacs: ah, right, I'm talking about things that gets installed as a dependency

13:11 <isaacs> augustl: yeah, you shouldn't lock down the deps of those things, either.

13:11 <isaacs> doing so only reduces the number of places where it can be used.

13:11 <isaacs> and reduces the feedback and usage that your lib will get.

13:11 <augustl> true, the Gemfile.lock only makes sense for things-you-deploy too

13:11 <isaacs> right

13:11 <isaacs> and gemfile.lock is a pretty sad substitute for just checking those things into git.

13:12 <aslant> Nested in the json body of an http request posted from the browser to a Node server, as well as other stuff, there's an empty array. The key-value pair competely disappears by the time I'm processing it. I'm using Express for the Web server and jquery on the client. Any ideas where the problem might be?

13:12 <augustl> isaacs: I think Gemfile.lock is the right thing to do

13:12 <waxjar> it's a great substitute for fast deployment

13:12 <isaacs> augustl: why?

13:12 <isaacs> waxjar: how is it "fast deployment" to have to talk to another web server to deploy?

13:12 <augustl> isaacs: the package manager manages packages, I shouldn't have to remember to check it into git

13:12 <isaacs> augustl: if you want them locked down, you do.

13:12 <isaacs> augustl: it's not hard.

13:12 <isaacs> npm install blah; git add node_modules; git ci -m "update blah"

13:12 <isaacs> create a bash shortcut for it.

13:13 <isaacs> :)

13:13 <augustl> isaacs: right, but it's still the package managers concern to make sure I have the correct versions of packages

13:13 <augustl> and the git repos job to keep track of my code

13:13 <isaacs> augustl: sure, and it will.

13:13 <augustl> it's a matter of opinion though

13:13 <isaacs> no, it's actually provable in this case.

13:13 <augustl> should the git repo track your code only, or the dependencies too

13:13 <isaacs> there are metrics we can measure, and have been measuring.

13:13 <isaacs> the dependencies are a part of "your program" if you're deploying them.

13:13 <isaacs> that's why node bundles v8

13:13 <isaacs> same reason.

13:14 <isaacs> it's a standalone application.

13:14 <waxjar> well, the servers at heroku fetch the gems from ruby gems/or cache a lot faster than my connection can upload them

13:14 <isaacs> waxjar: don't you use git to push stuff to heroku?

13:14 <waxjar> i do

13:14 <augustl> isaacs: I think it makes sense that node embeds v8 in the tarball you download. In the git repo a submodule should be used.

13:14 <isaacs> waxjar: don't they already have most of the diffs?

13:14 <isaacs> waxjar: your argument that heroku can fetch them faster than you upload them is thus invalid.

13:14 <isaacs> waxjar: you're not uploading most of them most of the time.

13:14 <isaacs> you're only uploading the changes.

13:14 <isaacs> augustl: submodules are unnecessarily painful.

13:15 <waxjar> meh, i guess it's not such a big deal

13:15 <isaacs> Gemfile.lock is a half-way solution to an invented problem.

13:15 <isaacs> that's not a package manager's job.

13:15 <augustl> isaacs: how is it half-way, and invented?

13:16 <isaacs> augustl: it's half-way because you don't get nearly the same level of guarantee that things are actually "locked"

13:16 <isaacs> augustl: with git you get a cryptographically secure sha.

13:16 <isaacs> if one byte is off, you know exactly which byte, and how off.

13:16 <augustl> isaacs: in case people republish version 1.3.2 you mean?

13:16 <isaacs> augustl: or in case the gem server goes down.

13:16 <isaacs> or is compromised.

13:17 <isaacs> it's an invented problem because really, what works much better, is to just check all your deps into git, and then deploy one single thing that has the entire app.

13:17 <isaacs> Gemfile.lock can never give you the same level of reliability or reproducibility

13:17 <isaacs> thats why there's no `npm lock` command.

13:17 <jesusabdullah> bundledDeps *are* pretty rad ^^

13:17 <isaacs> becuase it's dumb.

13:17 <augustl> it's interesting.. As long as you keep all 3rd party code in vendor/ in your project you can easily ignore that in git logs etc to only see changes to "your own" code

13:18 <isaacs> augustl: yeah.

13:18 <augustl> what about when you depend on a npm package that needs to be compiled?

13:18 <isaacs> augustl: and, you end up with the same number of commits that you'd have with submodules.

13:18 <CoverSlide> hey folks, anyone try to fire off a bunch of http.request 's at once and get getaddrinfo ENOENT errors?

13:18 <isaacs> augustl: run `npm rebuild` on deployment.

13:18 <isaacs> augustl: rebuild is a non-network command. it doesn't touch any remote resources. it just walks your dep tree runnig any install commands necessary.

13:19 <aslant> re: my question above. It's nothing to do with node or express, it either the browser or jquery

13:20 <augustl> the repo size still concerns me though. Same number of commits as a submodule, but it's N bytes for the commit instead of just one sha changing

13:20 <augustl> the node repo is now 44.3 mb, how much of that is changed dependencies?

13:20 <augustl> and will that be a problem in 3 years from now when it's 1.5gb large?

13:21 <augustl> just can't shake the feeling that embedding dependencies in the git repo doesn't scale

13:21 <isaacs> augustl: repo sizes are going up slower than disk size relevance is going down.

13:21 <isaacs> it's 44.3 mb? *no* node program is anywhere near that size.

13:21 <isaacs> that's including all of v8 and libuv and cares and openssl

13:22 <isaacs> oh, not cares any more

13:22 <augustl> I'm talking more in a general sense, not just node projects

13:22 <isaacs> http_parser, npm, v8, uv, and zlib

13:22 <CoverSlide> node executable is about 6mb last i checked, which is kind of big for a single executable; perl, python, ruby are around 500k iirc

13:22 <augustl> CoverSlide: it embeds a lot of stuff :)

13:23 <augustl> CoverSlide: all of ruby is a lot more than 500k

13:23 <CoverSlide> true, if you include the standard library

13:23 <isaacs> building as a standlone bin has a lot of advantages.

13:23 <augustl> isaacs: it has a lib/ folder too no?

13:23 <isaacs> augustl: the lib js files get compiled in

13:23 <isaacs> as c strings

13:24 <augustl> ah that's how it's done

13:24 <isaacs> yeah

13:24 <isaacs> so you can drop the node bin anywher.

13:24 <isaacs> it used to use a lib folder.

13:24 <CoverSlide> great we have to worry about the null byte too. where does the bloat end?

13:24 <isaacs> waaaayyyy back

13:24 <* isaacs> and augustl are showing our age...

13:24 <augustl> we'd probably want to do that for busterjs.org at some time. I.e. create something like node, an executable that inlines all of the buster code and is super easy to install

13:24 <isaacs> augustl: yeah, i'd sooo love to do that.

13:24 <isaacs> augustl: that'd be so nice for cli apps

13:25 <isaacs> just download the thing, and it runs. don't even have to know that node is a part of it

13:25 <augustl> indeed, almost don't need an installer, just download a file and put it in path :)

13:25 <augustl> yup

13:25 <tjfontaine> so evil

13:25 <DeezGz> MongoDB

13:25 <AvianFlu> we've had a similar dream of jitsu.exe for windows peeps

13:25 <isaacs> like a `nodecc` that bundles your program all into an exe and unix bin

13:25 <augustl> tjfontaine: well some people _really_ like convenience :)

13:25 <augustl> isaacs: gimme! :D

13:25 <isaacs> augustl: it's in the plans. there are other things to do first.

13:26 <CoverSlide> didn't ryah want a "node install" command

13:26 <augustl> isaacs: about the git repos and dependencies, I think I view dependencies and generated files as the same thing. As in, you wouldn't commit the output of "make" into the git repo.

13:26 <tjfontaine> I wish we could fork all these windowisms into a separate project

13:26 <augustl> but it's as you say different, dependencies are actually part of your program, not "generated files"

13:27 <tjgillies> Array(16).join("wat" -1) + " Batman!"

13:27 <CoverSlide> yes we all saw the wat video

13:27 <isaacs> augustl: that does kind of make sense if, for example, you have a .node file that one of the deps builds.

13:27 <CoverSlide> javascriptisms that people have known about for ages

13:27 <isaacs> augustl: you should probably put that in a gitignore or something.

13:27 <CoverSlide> that noone ever uses in real life

13:28 <tjgillies> CoverSlide: that fact, is the only thing that makes my statement funny

13:28 <augustl> woha, reboot time?

13:28 <CoverSlide> yay netsplits!

13:28 <Guest81666> hey, I'm a gues now

13:28 <Guest81666> this wasn't a netsplit I think..

13:28 <isaacs> Guest81666: yeah, it was

13:29 <isaacs> Guest81666: just /nick back to what you were

13:29 <augustl> way ahead of ya :P

13:29 <isaacs> Guest18468: 10:27 chrisdickinson has left IRC (*.net *.split)

13:29 <chrisdickinson> aww.

13:29 <* chrisdickinson> is flattered to be used as an example.

13:30 <augustl> I wonder why the peeps are laughing so much in that video. It's not _that_ funny...

13:30 <isaacs> augustl: batman jokes

13:30 <augustl> they must have had a professional audience warm up guy, like they have for talk show audiences

13:30 <CoverSlide> probably just a laugh track

13:31 <DeezGz> hello guys

13:32 <CoverSlide> hello males

13:33 <yenz> <laugh track>

13:33 <yenz> :D

13:35 <augustl> so that's what a netsplit looks like when you're being split. I always thought it was my router that failed every time I got back into irrsi as Guest123123

13:35 <augustl> or something else connection related on my end

13:38 <bruceb_> Greetings

13:48 <megalomix> hello everybody

13:48 <isaacs> hi

13:48 <DeezGz> hello guy

13:51 <CrawfordComeaux> Anyone able to suggest a module for signing OAuth'd API calls?

13:53 <chapel> CrawfordComeaux: node-oauth

13:53 <megalomix> hello

13:54 <megalomix> guys, I do not know WHERE...e WHEN

13:54 <megalomix> but node has a problem i think

13:54 <megalomix> i lunched an app

13:54 <megalomix> yesterday and today

13:54 <stride> stop eating your apps, problem fixed

13:54 <megalomix> and after around 10 hours

13:54 <stride> :)

13:54 <megalomix> the apps becomes idle

13:55 <megalomix> i see the process, but it seems idle

13:55 <megalomix> i also tried to see it with node-inspector

13:55 <megalomix> but nothing, no breakpoints are called

13:56 <megalomix> i do not know the problem.....the app works very good (And do the same thing)

13:56 <megalomix> then after X hours....it becomes idle

13:57 <megalomix> i also put breakpoints in node.js file

13:57 <megalomix> but nothing happen

13:58 <bruceb_> Can anyone point me in the direction of an apache benchmark-like app written in node? I don't care whether it uses the built-in http module, higher level http-based modules, or the basic net module only. I need to find out the best way to creat concurrent http connections. :)

13:59 <markq> anyone know what express-mongoose is supposed to hep me with?

13:59 <DeezGz> i was trying to figure out my self

13:59 <markq> I'm not very familiar with promises but it almost seems like a pseudo transaction type thing

13:59 <CoverSlide> i think it's a session store based on mongo

14:00 <markq> isn't that mongostore though?

14:00 <DeezGz> is their a way to compile the MongoDB driver directly in the node.exe

14:00 <CoverSlide> i dont know, i know there's a redis store, i'm assuming they made a mongo store

14:00 <markq> DeezGz: part of node-core?

14:00 <DeezGz> compile it with the node.exe

14:01 <markq> ah

14:01 <markq> i don't know

14:01 <DeezGz> so i dont have to carry it around

14:01 <CoverSlide> maybe stick it into the lib/ directory

14:01 <megalomix> isaacs, do you have any idea? or can you advice me a check that i can do? as i told, the apps works good, and does the same things again and again...but after many hours becomes idle

14:02 <isaacs> DeezGz: you'd have to fork node and add it as a module to the src/ dir. we're not ever going to take such a patch into core, though, so you'd be on your own.

14:03 <isaacs> DeezGz: your best bet is to just not do this.

14:03 <tjfontaine> out in the wilderness, left to die alone

14:03 <DeezGz> well i just want to add the .js to the node.exe

14:03 <isaacs> DeezGz: yeah. deploy the js and exe together.

14:03 <jesusabdullah> So, I was poking around Alameda on google maps and I found what looks like an exploded airliner

14:03 <isaacs> DeezGz: use what node already does.

14:03 <jesusabdullah> http://maps.google.com/maps?ll=37.790757,-122.322856&spn=0.001027,0.001632&t=h&z=20

14:03 <DeezGz> i already made a mime.js and compiled it with node js

14:03 <DeezGz> is possible

14:03 <isaacs> DeezGz: so, do the same thing with mongo, then

14:04 <isaacs> DeezGz: but you have to compile it in your own fork.

14:04 <isaacs> the mongo driver is quite a bit bigger, and probably not written with this approach in mind.

14:04 <tjfontaine> all this "compile" talk, makes me think something is being lost in translation

14:04 <DeezGz> yea that is the problem i am having

14:05 <markq> jesusabdullah: O_O

14:05 <DeezGz> its way to big and not very clear and clean

14:05 <augustl> node should embed mongo and browsers should embed jquery :D

14:05 <DeezGz> i dont even know where to start to get it going

14:05 <DeezGz> its a database driver for god sake, node is open source right?

14:05 <markq> I'm waiting for the day in which I can just tell a robot to program everything from scratch

14:06 <tjfontaine> DeezGz: and as isaacs said, you're free to fork it

14:06 <augustl> markq: isn't that kind of what programming is like today? :)

14:06 <DeezGz> well if we start a structure to make this possible, we wont have a problem like this

14:06 <markq> fork it and then spoon in mongo

14:06 <markq> don't use a knife though

14:06 <DeezGz> only root lib forder for your modules

14:06 <tjfontaine> DeezGz: "we" don't have any problem, "you" have a wish

14:07 <DeezGz> think about it, when you want to compile like a comman database driver it would be possible

14:07 <markq> DeezGz; it just isn't going to happen. ever. totally against node-core philosophy

14:07 <DeezGz> well it has aleady happen. i already dont it with my mime.js

14:07 <DeezGz> next is mongodb driver

14:08 <DeezGz> then sql driver

14:08 <DeezGz> the mysql drive

14:08 <tjfontaine> ...

14:08 <DeezGz> -r

14:08 <bruceb_> I've been testing a node crawler designed to politely crawl as many sites concurrently as possible, but it seems like the sockets just queue and connect serially? I'm running the latest node.js v0.6.8 (I built it yesterday).

14:08 <isaacs> DeezGz: these things do not belong in node-core.

14:08 <tjfontaine> Profit

14:08 <isaacs> DeezGz: do them as addons.

14:08 <isaacs> DeezGz: you're trying to scale a very high wall when there's a door already there for you.

14:08 <isaacs> the pain of "having to carry the js around with you" is WAAAYYYY less than what you're trying to do.

14:09 <bruceb_> It takes upward of 16 seconds to get 300 sockets connected at all (I log connections whether they're currently active or not, all of my statistics are sanely gathered)

14:09 <bruceb_> I've tested with the net module handling HTTP requets myself, with the built-in http module, and with two third-party higher level http modules (I tried those first)

14:09 <DeezGz> easy to say when sitting on file system, but when you have to make these things move around in a portable way, it becomes a nightmare

14:10 <Phoenixz> Can I do two times modules.exports = variableName; ?

14:10 <jesusabdullah> markq: I think it's a firefighter training facility

14:10 <tjfontaine> DeezGz: have you not met configuration management/souce control?

14:10 <tjfontaine> DeezGz: you're talking about a deployment problem

14:11 <DeezGz> you see how the node.js source has done, very clean, that is the way to do source

14:11 <DeezGz> no module structure problem

14:11 <DeezGz> and debuging clearity problem

14:11 <chjj> mime.js in node core? i hope that never happens

14:12 <DeezGz> sorry guys Notepad++. keep it simple

14:12 <chjj> there is no specification which maps file extensions to mime types

14:12 <chjj> could be anything

14:12 <DeezGz> i put it in my own compiled node.exe

14:12 <DeezGz> i compile my own node.js

14:12 <augustl> DeezGz: hmm, I'm curious, why did you do that?

14:13 <augustl> most of us add it as a dependency in package.json :)

14:13 <DeezGz> i didnt want to car the mime.js file with the node.exe and my app with me every where

14:13 <augustl> or check it into the repo for the program

14:13 <DeezGz> carry sorry

14:13 <augustl> you didn't want to carry mime.js with node.exe?

14:13 <chjj> DeezGz: im curious, why didnt you just put mime.js in your app's codebase?

14:13 <augustl> isn't that the default behaviour?

14:13 <augustl> as in, node.exe doesn't bundle mime.js

14:14 <DeezGz> for codebase setups, yes, this is straight up notepad++ and my web app in a node.exe

14:14 <DeezGz> thats what i wanted

14:14 <augustl> I don't follow you at all. What's mime.js got to do with nodepad++

14:14 <augustl> ?

14:15 <DeezGz> i also wanted a mongodb driver in ther too. that mongo thing is all over the place

14:15 <DeezGz> meaning i code this my self and edit the config stuff my self manually

14:15 <DeezGz> no automation

14:15 <DeezGz> i dont mind

14:15 <bruceb_> Does anyone know about a nodejs crawler project that can handle lots of different jobs in parallel?

14:15 <augustl> I still don't understand what you're talking about. "straight up notepad++ and my web app in a node.exe" makes no sense to me..

14:16 <DeezGz> but that module structe i see some of these projects using does not make any sense

14:16 <chjj> augustl: isnt it obvious? he compiled notepad++ and linked it with node

14:16 <chjj> :)

14:16 <DeezGz> notepadd++ is a text editor on windows

14:16 <DeezGz> no no no

14:16 <augustl> right, with you so far :)

14:16 <chjj> hehe

14:16 <DeezGz> it is what i use to edit these files

14:17 <augustl> so what do you do with notepad++ that makes you want to compile mime.js into a custm node.exe?

14:17 <augustl> or is it related to notepad++ at all?

14:17 <DeezGz> no script or codebase managment software

14:18 <augustl> DeezGz: can you describe your exact problem in one sentence?

14:18 <DeezGz> well i want to gointo the mongoDB driver and make it into a coule or posible 1 js, then compile into the node.exe

14:18 <DeezGz> couple sorry

14:18 <augustl> right, but what problem do you solve when you compile mongo into node.exe?

14:19 <bruceb_> he solves the problem of "having to cart those files around along with node" as he mentioned above.

14:19 <DeezGz> thx yes

14:19 <bruceb_> unless I misunderstood him earlier

14:19 <DeezGz> i have alot of work to do

14:19 <augustl> so you carry node.exe around with you? Do you reinstall windows often or change computers often or something?

14:19 <DeezGz> yes i am a vmware exsi guy

14:19 <augustl> and you want a node.exe on a usb stick you can carry around, that embeds some projects you use often?

14:19 <DeezGz> so yes

14:20 <DeezGz> i have 5 systems running right now

14:20 <augustl> what's the downside of depending on mongo in package.json and linking it in with npm?

14:20 <DeezGz> yes or will use often

14:21 <DeezGz> carry all the file directorys and writing script to handdle many files and sub directorys

14:21 <augustl> you don't have to write a script to handle dependencies - npm does that

14:21 <DeezGz> vs handling 1 file

14:21 <augustl> just type "npm link" in the project one time and you're done

14:22 <DeezGz> what does this npm do?

14:22 <bruceb_> node package manager :P

14:22 <DeezGz> supposed to be like a apt-get on ubuntu huh!

14:22 <bruceb_> think apt or yum, but for node dependencies and much less bulky

14:22 <augustl> DeezGz: yes, it's like apt-get

14:22 <augustl> npm is a package manager too

14:23 <DeezGz> but it cant gather these modules to compile in your node.js src? right

14:23 <DeezGz> i think that is a missing feather

14:23 <augustl> no, but it solves the problem of managing the software

14:23 <augustl> just type npm link and you have all the dependencies installed

14:24 <jamescarr> ls

14:24 <DeezGz> npm dows work nice with getting the package but that it

14:24 <jamescarr> shit

14:24 <bruceb_> DeezGz: try it, spin up a new vm and install node, then copy your project requiring mongo etc. onto the machine. Then type node link

14:24 <augustl> DeezGz: no, it also installs it, in addition to downloading it

14:24 <augustl> DeezGz: it puts the packages in a place so that require("thepackage") works

14:24 <DeezGz> id it already that how i got mongodb on my system

14:25 <DeezGz> i want to consolidate this mongoDB into one js file

14:25 <isaacs> DeezGz: we were discussing earlier this problem.

14:25 <augustl> why do you want to consolidate mongodb into one file?

14:25 <DeezGz> can npm help me with that?

14:25 <isaacs> DeezGz: it'd be nice to be able to compile a node program into a single standalone executable binary

14:25 <augustl> DeezGz: you don't seem to get what I'm saying

14:25 <isaacs> DeezGz: but that functionality does not exist today.

14:25 <isaacs> DeezGz: what you really are asking for is a nodecc program, similar to javacc

14:26 <isaacs> DeezGz: that is not a priority yet.

14:26 <augustl> DeezGz: if you use package.json you don't need to build it into node.exe

14:26 <DeezGz> i do, but u dont seem to under stand 1 file, u like package managers

14:26 <augustl> perhaps I don't understand your problem

14:26 <isaacs> augustl: he wants nodecc

14:26 <jamescarr> isaacs, didn't I hear that the new V8 release supports vm snapshots?

14:26 <augustl> you don't want node.exe with mongodb, you want your node project and all its dependencies as one .exe file?

14:26 <DeezGz> people we have a lot to learn here

14:26 <isaacs> augustl: bingo.

14:27 <jamescarr> isaacs, yep: With the V8 snapshot feature (activated with build option snapshot=yes, which is the default) the time spent creating the first context will be highly optimized as a snapshot includes a serialized heap which contains already compiled code for the built-in JavaScript code. Along with garbage collection, V8's extensive caching is also key to V8's performance, for more information see V8 Design Elements.

14:27 <DeezGz> yes thnks augustl

14:27 <isaacs> DeezGz: would it be ok for your program to be all in one place, even if it wasn't called "node.exe"?

14:27 <isaacs> that doesn't exist yet.

14:27 <augustl> DeezGz: I think the problem here is that when I asked you to explain what your problem was, you didn't do a very good job of doing so ;)

14:27 <DeezGz> well it has to be called node.exe

14:27 <augustl> or that I'm brainfarting, who knows..

14:28 <isaacs> DeezGz: why?

14:28 <bruceb_> august1: I can explain my problem pretty clearly, and you seem pretty familiar with node. Do you have a moment?

14:28 <DeezGz> brb guys

14:28 <augustl> bruceb_: I'll go find august1 and see what he says

14:28 <* isaacs> beginning to think that DeezGz's problem is overly constrained

14:28 <jamescarr> isaacs, yeah :)

14:28 <tjfontaine> itym DeezGz's WishList

14:28 <bruceb_> l1 :)

14:29 <augustl> bruceb_: get a better font!

14:29 <bruceb_> I'm attempting to write an http crawler in node, both because I like node and because I think it would be pretty fast. I realize that node was primilary designed for server-side javascript execution but this seems like a lot less code in node than in java using nio

14:30 <augustl> isaacs: I liked the old blue/purple links in the docs better than the green/gray ones :P

14:30 <augustl> isaacs: on my screen it looks like two different colors, not like a slightly faded version of the green color, just fyi

14:30 <bruceb_> My tests however have revealed slow socket connections being made.. It's not my ulimit as I never even reach 1k. It takes upward of 16 secs to establish connections on 300 sockets and I'm not sure why. Mind you each socket is connecting to a different domain, so I'm being polite about it.

14:31 <bruceb_> I suspect my code first, obviously, as I suspect a bug in the language last. I'm 99% it's my code but I don't know why this is happening

14:31 <tjfontaine> bruceb_: is the code available for inspection?

14:32 <augustl> perhaps DNS lookup is what's slow

14:32 <bruceb_> it can be :)

14:32 <bruceb_> I have three tests actualy, one using the net module only

14:32 <tjfontaine> bruceb_: you will get more useful information if you can provide the most context

14:32 <augustl> seems like every dns lookup when connecting does require('dns')

14:32 <augustl> perhaps that's what's slowing it down

14:32 <bruceb_> one using http module, and one using a third-party module that's higher level but I've sort of ditched that.

14:32 <augustl> but I suppose the require of an internal module is fast, since it doesn't have to go to the file system

14:32 <bruceb_> I'll give as much context as you like. What is unclear?

14:33 <augustl> ah, the http module has agents that pools etc

14:33 <bruceb_> yeah I have used htis

14:33 <augustl> g2g

14:33 <bruceb_> I changed maxSockets and such. I'm using the new agent correctly as far as I can tell (the docs are oudated on this afaik)

14:34 <DeezGz> node.gyp

14:34 <tjfontaine> bruceb_: the most context is to be able to see the code in question, then those who are equipped can provide useful hints

14:34 <bruceb_> Where can I post the code for inspection? What's the most convenient for you?

14:34 <tjfontaine> gist.github.com

14:35 <bruceb_> omw

14:37 <bruceb_> alright, here's the http test: git://gist.github.com/1690517.git

14:37 <bruceb_> this is just me trying to get lots of parallel connections happening. At this point I'm just counting time to see how long it takes to establish connections etc.

14:38 <bruceb_> mind you targets.txt is a text file containing actual URLs, mostly to index pages of sites. I've got just over 900 urls in there and they are mostly working :)

14:38 <bruceb_> Ah to be more clear, most of the URls are valid and actually return a payload of html when a get request is issued, I think a few are down/offline at any moment though.

14:41 <bruceb_> I realize that I'm probably doing something terribly wrong here, but I don't know what it is :) The test runs fine but it just seems slow making connections.

14:41 <bruceb_> am I just blocking as a result of reading data from so many remote hosts and that's what's happening here?

14:42 <DeezGz> maybe your connection pool limit is too low

14:44 <bruceb_> I've ready more than a couple forum posts on this, it seems there was a bug in an earlier version of node that caused a problem with socket queueing

14:44 <bruceb_> *read

14:44 <bruceb_> tjfontaine: One of my targets.txt lists is just a csv dump of the top 1000 alexa-ranked sites

14:45 <bruceb_> converted to txt of course

14:47 <dob_> do you know where i can find the eclipse plugin for node development? I had this plugin and thought it was great.

14:47 <dob_> I loved the node start and stop button...

14:53 <bruceb_> isaacs: Are you available to field a socket pooling/concurrency question?

14:54 <lbod> hi guys, im a behind a corporate firewall at work and before i start asking them for firewall rules im right in thinking i can just download tarballs/zips from github without using npm (as long as i update nodes package.json)?

14:55 <lbod> ive done it with a couple so far but im looking at template engines now and theres a few dependencies

14:55 <tjfontaine> lbod: the firewall blocks npmjs.org but allows github.com?

14:56 <lbod> yep, npm uses httpclient? we use pac files for browser access

14:57 <lbod> its more a case of non ntlm client not being granted access i.e. through browser pac files

14:57 <torvalamo> maybe npm should accept proxies then

14:57 <isaacs> lbod: yes, npm uses the request module.

14:57 <isaacs> npm does support basic auth http and https proxies.

14:58 <isaacs> but it doesn't do the CONNECT dance to tunnel https through http, so if your proxy doesn't speak https, then you have to use the http registry url.

14:58 <isaacs> which is less secure.

14:58 <tjfontaine> if he says ntlm I'm walking away

14:58 <isaacs> ntlm is insanity. probably never going to support that.

14:58 <tjfontaine> I would never expect you to

14:58 <lbod> am i right in thinking i can just download though? as long as i get the dependencies

14:58 <isaacs> it'd be easier to just write a standalone server that translates ntlm to basic auth.

14:59 <isaacs> lbod: sure. you can also just fetch tarballs and unpack them right into node_modules.

14:59 <lbod> this is just so i dont have to run through hoops asking the network guys to let me out

14:59 <isaacs> lbod: or you can tether through your cell phone :)

14:59 <isaacs> lbod: or take your laptop to starbucks.

14:59 <isaacs> probably less headaches doing it that way

14:59 <isaacs> :)

14:59 <torvalamo> or sacrifice a child

14:59 <tjfontaine> ssh -D

14:59 <torvalamo> that always works

14:59 <lbod> isaacs: excellent, cheers.. like i say ive done it with a cpl of modules so far

14:59 <torvalamo> ALWAYS

14:59 <DeezGz> openvpn home

15:00 <DeezGz> the best

15:00 <isaacs> lbod: yeah, you can also set up an SSH tunnel through a server on the outside, and use that as your registry url.

15:00 <DeezGz> ssl too

15:00 <zeile> guys, whats the common way to put css into my static node.js server. jade?

15:00 <tjholowaychuk> zeile link tags?

15:00 <tjholowaychuk> in html

15:00 <isaacs> then have it proxy its connection to registry.npmjs.org:443

15:01 <torvalamo> style attributes in your tags bro.. go hardcore

15:01 <megalomix> why my application goes idle when it runs for 12-14 hours :((

15:01 <lbod> isaacs: this is more for my own playing whilst at work, i get to play alot but corporates/financial services are a pain to work in

15:01 <isaacs> lbod: tell me about it :)

15:01 <isaacs> lbod: every new service that wants to do anything on the network has to sacrifice goats.

15:01 <isaacs> to the gods of IT

15:01 <lbod> yep

15:01 <DeezGz> json you css so it is easy to work with javascript

15:01 <lbod> and you call favours etc

15:01 <zeile> dont wanna go hardcore :d

15:02 <bruceb_> IT is a service, and its customers are the rest of the company :)

15:02 <DeezGz> yes am a it guy

15:02 <zeile> is stylus the way to go?

15:02 <lbod> somones about to say "treating customers fairly"

15:02 <zeile> im on express btw..

15:02 <bruceb_> Unfortunately they usually behave like DMV employees

15:03 <DeezGz> in it its every man for himself sorry to say

15:03 <bruceb_> "serving" the community that way

15:03 <tjholowaychuk> zeile whatever you want, regular CSS / Stylus / LESS

15:03 <tjholowaychuk> whatever works for you

15:03 <lbod> so in regards to the depenencies, it feels a bit hacked if im not using npm but can i specify > than versions in package.json?

15:04 <zeile> im not used to so much freedom :d but ill look into stylus a bit more. found the page :D

15:04 <megalomix> guys, do you know acommand the trace a process?

15:04 <bruceb_> you can't trace in node, there is no stack to speak of