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

Commit Graph

Author	SHA1	Message	Date
Ryan	9b3baf3d50	Bugfix: node.encodeUtf8 was broken. (Connor Dunn) http://groups.google.com/group/nodejs/browse_thread/thread/5ad0660a0959d885#	16 years ago
Ryan	e111ccc014	Add Felix Geisendörfer's HTTP stress test. Does not pass on Macintosh and FreeBSD.	16 years ago
Ryan	4f46c47773	node.fs.File was not passing args to promise callbacks. Reported by Jacob Rus.	16 years ago
Ryan	9d3ed1bb92	Bugfix: negative integers in raw encoding stream. Add test. Reported by Tim Caswell.	16 years ago
Ryan	b27f8ba06d	Default to chunked for client requests without C-Length. Also add test. Reported by Felix Geisendörfer.	16 years ago
Ryan	41d89f611f	Add DNS API. Missing functional tests. I'm not sure how to do tests because I don't want to rely on the fact that users have an internet connection.	16 years ago
Ryan	d41197e02c	Disable test-tcp-many-clients.js. It's broken on macintosh - don't want to fix right now.	16 years ago
Ryan	b1588e78d9	Fix utf8 scripts, add test. Thanks Urban.	16 years ago
Ryan	1b6bbc619d	Bugfix: Server-side clients not attached between creation and on_connect. Solution is to manually add Attach() to OnConnection. For client side it seems there is no Detach() being called after NS resolution? Otherwise I would have removed it. That was another bug. Note: We don't want to modify evnet's behavior to have on_connect called directly when the socket is accepted. evnet needs to support SSL, and on_connect is supposed to signal that the SSL connection is established. The point here is that being "connected" and being "attached" to the event loop are two different things. SSL stuff may be transmitted when a socket is not "connected" but it must always be attached.	16 years ago
Ryan	5e2a6f8c46	Upgrade evnet to fix close() bug. Add test for bug. evnet wasn't properly closing sockets if they didn't have data to write.	16 years ago
Ryan	041af82b8c	Bugfix: Sockets not properly reattached if reconnected during disconnect event. The problem was that Connection::on_close was calling Detach() directly after executing the "disconnect" event. Since we had a boolean attach count, this was leaving sockets detached even if they had reattached in during the event. * Added many asserts in http.cc and net.cc to ensure that sockets are connected when they should be. * Changed ObjectWrap to use a reference count instead of boolean attached_ value. * Fixed similar bug in Timer.	16 years ago
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

1 2

77 Commits (e46a832ded249b44ea94523a796c4e2847a104ab)