expressjs / express Goto Github PK

As far as I can tell, you have a synchronous request handling.

Consequently, you will fail at

• receiving any request body
• integrating any type of backend

Just letting you know, because I am working on a node.js framework myself and did the exact same mistake at the beginning.

for JSON / XML etc

only cache in production env,
make sure that contrib view engines have options
to disable their own caching

when client accepts html

No need to dink around with browser discrepancies here

Jack...

fix / refactor into own file and specs

with "public" directory setting, ensure test -f

With halt()

cuts rps down by 1/3, date formatting == slow

addedRoute etc

init args in module context.. and hooks in mod context so for example

use(DefaultContentType, 'text/html')

as func args

and options like sinatra supports for raising errors, etc

Add rawBody so the decoder module can support arbitrary body decoding

VS similar frameworks

adjust core as needed

With a bit of closure magic we should be able to provide utility functions
to routes without this. Also now we may consider:

get('/user/:id/:operation', function(id, operation){

})

with common logger and profiler

check back on the nodejs group

get(':filename.css', static) // something like this

Add some rendering hooks, only really needed
once we have ORM support so we can see what
is impacting performance

param('id') becomes '1/foo'

Use Break for iterators

replace unescape

So Profiler can wrap leading / trailing triggers etc