expressjs / express Goto Github PK

VS similar frameworks

replace unescape

Use Break for iterators

and options like sinatra supports for raising errors, etc

So Profiler can wrap leading / trailing triggers etc

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

with "public" directory setting, ensure test -f

check back on the nodejs group

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

})

for JSON / XML etc

with common logger and profiler

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.

when client accepts html

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

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

With halt()

addedRoute etc

Add rawBody so the decoder module can support arbitrary body decoding

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

use(DefaultContentType, 'text/html')

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

as func args

No need to dink around with browser discrepancies here

fix / refactor into own file and specs

Jack...

adjust core as needed

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