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

487 Commits

131 Branches

446 Tags

325 MiB

Tree: 723c7d9f7c

Commit Graph

Author	SHA1	Message	Date
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	16 years ago
Ryan	65ec2d5db4	Fix http benchmark. Wasn't correctly dispatching.	16 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

Author

SHA1

Message

Date

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

16 years ago

Ryan

65ec2d5db4

Fix http benchmark. Wasn't correctly dispatching.

16 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

3 Commits (723c7d9f7c4e5ba9600adae95bd481fad70a3d60)