9 Commits (ea29e137b5a9acda27bd9601448639aacfc1cd9e)

Author	SHA1	Message	Date
Ryan	116f4dea05	lint	2009-08-26 22:14:45 +02:00
Ryan	723c7d9f7c	Replace onExit() with process.addListener("exit") ... - Update documentation. - Depreciation message for onExit().	2009-08-26 22:14:44 +02:00
Ryan	31265be4a6	Depreciate onLoad	2009-08-26 22:14:44 +02:00
Ryan	7aaab320b3	API: tcp.Connection "disconnect" event renamed to "close". ... More semantic, since the event will be emitted on connection error, when the connection was ever established.	2009-08-14 12:51:46 +02:00
Ryan	8047b912c0	Change 'new node.tcp.Connection' to 'node.tcp.createConnection'	2009-06-30 13:56:52 +02:00
Ryan	d428eff023	Snakecase events .	2009-06-29 13:18:30 +02:00
Ryan	ed926da691	Remove onEvent compatibility	2009-06-28 19:08:26 +02:00
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.	2009-06-28 19:08:26 +02:00
Ryan	3fed1a0954	Use v8's test runner	2009-06-22 14:08:42 +02:00