5 Commits (0f888ed6de153f68c17005211d7e0f960a5e34f3)

Author	SHA1	Message	Date
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	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.	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