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

Author	SHA1	Message	Date
Ryan Dahl	7c1c89fc29	Update benchmark script to new API	15 years ago
Ryan Dahl	ae85d9af97	API: Make request/response object closer to stream interface - sendBody() renamed to write() - 'body' event renamed to 'data' - 'complete' event renamed to 'end'	15 years ago
Christopher Lenz	f8ba9c3bc9	Add http.Client.prototype.request() Change the http.Client API so that it provides a single request() method taking an optional parameter to specify the HTTP method (defaulting to "GET"), instead of the five methods get(), head(), post(), del() and put().	15 years ago
Ryan Dahl	d582599c14	Upgrade benchmark scripts for new module API	15 years ago
Ryan Dahl	ad0a4cefb8	Namespace EVERYTHING under process; introduce GLOBAL http://groups.google.com/group/nodejs/browse_thread/thread/1034fd2ad2cd93e8	15 years ago
Ryan Dahl	04e53cab90	Rename node.libraryPaths to require.paths to be more inline with CommonJS.	15 years ago
Ryan Dahl	f6657c3c9d	Move http library to /http.js	15 years ago
Ryan	ad9d683f9f	API: rename node.Process to node.ChildProcess This is to avoid confusion with the global "process" object, especially for the instances of node.Process.	15 years ago
Ryan	316e2833f0	Use flat object instead of array-of-arrays for HTTP headers. E.G. { "Content-Length": 10, "Content-Type": "text/html" } instead of [["Content-Length", 10], ["Content-Type", "text/html"]]. The main reason for this change is object-creation efficiency. This still needs testing and some further changes (like when receiving multiple header lines with the same field-name, they are concatenated with a comma but some headers ("Content-Length") should not be concatenated ; the new header line should replace the old value). Various thoughts on this subject: http://groups.google.com/group/nodejs/browse_thread/thread/9a67bb32706d9efc# http://four.livejournal.com/979640.html http://mail.gnome.org/archives/libsoup-list/2009-March/msg00015.html	15 years ago
Ryan	65ec2d5db4	Fix http benchmark. Wasn't correctly dispatching.	15 years ago
Ryan	05d6319fa0	Add benchmark scripts. To use the benchmarks: node benchmarks/run.js or: make benchmark The numbers reported are the elapsed milliseconds the script took to complete. Currently only benching HTTP code and timers.	16 years ago