lukechilds/node - node - Gitea: Git with a cup of tea

Commit Graph

Author	SHA1	Message	Date
Joshaven Potter	4b9f26c51a	validate js	16 years ago
Ryan	7879e7fd25	small cleanups	16 years ago
Ryan	8047b912c0	Change 'new node.tcp.Connection' to 'node.tcp.createConnection'	16 years ago
Ryan	d56552dc66	Remove node.Process constructor from API	16 years ago
Ryan	e4ba665c87	Fix ref/unref problem. Was doing opposite of what I should.	16 years ago
Ryan	88ad880556	Add new test for node.fs.stat()	16 years ago
Ryan	d428eff023	Snakecase events .	16 years ago
Ryan	e876d6629e	Fix unused variable warnings.	16 years ago
Ryan	65324866bc	Implement Promises for file i/o	16 years ago
Ryan	ed926da691	Remove onEvent compatibility	16 years ago
Ryan	70fe920fb5	Use events for all HTTP messages. This is a rather large refactor! Mostly for the better side. I've had to remove some functionality like req.interrupt(). A lot of other work is left messy or incomplete.	16 years ago
Ryan	ed3d6a63d5	Further expand EventEmitter to TCP and HTTP The constructor for TCP servers can no longer take a connection handler for purely technical reasons. (The constructor for EventEmitter is implemented in C++ but addListener is in javascript, and I don't want to make too many C++ -> Javascript references.) Thus I introduce new constructor methods to ease the creation of the servers: node.tcp.createServer() node.http.createServer() These work almost the same as the old constructors. In general we're working towards a future where no constructors are publicly exposed or take arguments. The HTTP events like "on_uri" are not yet using the event interface. onMessage still is a constructor - but this will change soon.	16 years ago
Ryan	5b7fb1003c	Add failing test. Process spawning loop. I think this is the issue Felix Geisendoerfer is reporting: http://groups.google.com/group/nodejs/browse_thread/thread/efbae1ec1e67786c	16 years ago
Ryan	bdad5e7333	test-process-kill: start process after onLoad	16 years ago
Ryan	7363ccd273	bugfix: Properly exit a process. This requires that onExit() is not called immediately upon receiving a SIGCHLD. There could still be data in the pipez. So, instead just set a flag and invoke the pipe watchers. Sometimes one will not receive an EOF from pipes because the process was killed by a SIGTERM, or something. If SIGCHLD has been recved but we are getting EAGAIN, the pipez need to be closed too.	16 years ago
Ryan	3fed1a0954	Use v8's test runner	16 years ago

16 Commits (22c3a1e2a5cb9b6fa06e822af74f54c39e4eb61c)