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

Commit Graph

Author	SHA1	Message	Date
Ryan Dahl	5aadeae888	Simply C++ event emitter	15 years ago
Ryan Dahl	45a806a066	Statically define symbols ~7% improvement in hello world HTTP response bench.	15 years ago
Ryan Dahl	4d818f1fd3	Implement promises entirely in JS	15 years ago
Ryan Dahl	efe34f5023	Only allow a promise to fire once, remove promise.cancel() promise.cancel() is due to return at some point.	16 years ago
Ryan Dahl	a5df0f6a65	Prefix all source files with node_	16 years ago
Ryan Dahl	76f4962636	Bugfix: EIOPromise::Create was allocating two EIOPromise objects This is because it would call the javascript initializer which executed Promise::New, and then it would rewrap the handle. Instead I make an explicit inheritance from EIOPromise to Promise. This seems to fix a memory leak which was reported by Ray Morgan: http://groups.google.com/group/nodejs/browse_thread/thread/e38949b1989da1d7	16 years ago
Ryan	227638bac1	Lint	16 years ago
Ryan	747d6723aa	Clean up eio wrappers. Create EIOPromise.	16 years ago
Ryan	aefbd57514	Add stack to promise.wait(). The problem was that if promise A was waiting and promise B was created and then also told to wait (from some callback coming off the event loop), and then promise A finished, promise B's wait would return. Promise A's wait would not return until promise B was finished. This is incorrect. To solve this issue properly, one probably needs to allocate separate execution stacks. I use, instead, Poor Man's Coroutines. We continue to use the main execution stack and force promises created most recently to return first. That is even if Promise A finishes first, neither wait() returns. Not until Promise B finishes, will its wait() return. After that is complete, Promise A's wait() will return. This introduces the problem of growing the "wait stack" infinitely. Thus I've added a strong warning to the documentation only to use this operation sparingly. require() and include() seem to be the proper use case for such a thing: they are called usually at program start up - they don't take too long to finish and they won't be called so often. Let's experiment with this stop-gap. If the infinite promise stack becomes a problem for many, then I will remove promise.wait() entirely or perhaps only use it for thread pool events.	16 years ago
Ryan	116f4dea05	lint	16 years ago
Ryan	6025da2153	Introduce 'process' object. Also is the global object.	16 years ago
Ryan	19f182a39f	Experimental support for Promise.block()	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	842eaf446d	Move EventEmitter.prototype.emit() completely into C++. This shows a healthy speed up.	16 years ago
Ryan	1fc4dce08b	Simplify and cleanup ObjectWrap. Simplify and inline ObjectWrap::Wrap Inline and clean up ObjectWrap::Unwrap Move ObjectWrap into its own file. Remove handle from ObjectWrap constructor. add obj->Wrap(handle) Simplify Attach/Detach in ObjectWrap Remove ObjectWrap::InformV8ofAllocation. (Too messy/complex.)	16 years ago
Ryan	65324866bc	Implement Promises for file i/o	16 years ago
Ryan	7cd09874c6	Add Promise class	16 years ago
Ryan	2ecd7ffe54	in the middle putting in event code. broken.	16 years ago

5 Commits (b6c66f735bf34621e0bcdfbdff47c10b6458bc7a)