expressjs / express Goto Github PK

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

use(DefaultContentType, 'text/html')

VS similar frameworks

Use Break for iterators

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

Jack...

and options like sinatra supports for raising errors, etc

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){

})

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.

Add rawBody so the decoder module can support arbitrary body decoding

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

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

fix / refactor into own file and specs

adjust core as needed

when client accepts html

replace unescape

No need to dink around with browser discrepancies here

With halt()

with "public" directory setting, ensure test -f

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

So Profiler can wrap leading / trailing triggers etc

addedRoute etc

check back on the nodejs group

for JSON / XML etc

with common logger and profiler

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

as func args