4 ms·
From the official announcement https://groups.google.com/forum/m/#!topic/nodejs/fqBTNLwhEAI https://groups.google.com/forum/m/#!topic/nodejs/fqBTNLwhEAI Th
by bfm 15y ago
From the official announcement https://groups.google.com/forum/m/#!topic/nodejs/fqBTNLwhEAI https://groups.google.com/forum/m/#!topic/nodejs/fqBTNLwhEAI
The main advantages/differences over Connect/Express at this point are:
- Patterned after WSGI/Rack. This implies some significant differences in the API.
- Built on node 0.4; takes full advantage of streams.
- Built-in support for streaming multipart parsing/file uploading (uses node-formidable's parser).
- Built-in support for gzip encoding, URL rewriting, and URL mapping.
- RFC-compliant support for content negotiation using the Accept, Accept-Language, Accept-Encoding, and Accept-Charset HTTP headers.
- A specification with middleware to enforce it.
- dreamdu5t 15y agoSo nothing? Streams, multiparts, gzip, that is all in Connect/Express. I'm sorry but adhering to some spec that few people use or care about is hardly an advantage over Connect. Wouldn't it be trivial for Connect to adhere to the spec anyways? tjholowaychuk has done extensive testing/benchmarking of Connect/Express. I'd really like to see some benchmarks and code coverage.