expressjs / express Goto Github PK

VS similar frameworks

No need to dink around with browser discrepancies here

for JSON / XML etc

So Profiler can wrap leading / trailing triggers etc

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

use(DefaultContentType, 'text/html')

and options like sinatra supports for raising errors, etc

with common logger and profiler

addedRoute etc

with "public" directory setting, ensure test -f

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

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.

as func args

Add rawBody so the decoder module can support arbitrary body decoding

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

})

when client accepts html

Use Break for iterators

With halt()

adjust core as needed

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

Jack...

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

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

check back on the nodejs group

replace unescape

fix / refactor into own file and specs

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