Bret, quick question. Does the framework support an esi type tags to abstract out personalized info? thanks!
Suffices to say, no, we do not support that :)
31–40 of 77 posts
Bret, quick question. Does the framework support an esi type tags to abstract out personalized info? thanks!
Suffices to say, no, we do not support that :)
Awesome to see more Python webservers coming to light, and fast ones at that. One observation though; anyone else notice that the bar chart is a bit misleading? It compares running Tornado in 4 processes behind nginx to running Django behind Apache and Cherrypy as a single Python process. As a fellow coworker put it, "With 4 extra processes running of course it will be 4 times as fast." I'm not opposed to this kind o…
Apache/mod_wsgi creates multiple processes (or can). The issue is that Facebook didn't tell us what configuration settings they used. Did they limit the number of processes? Did they not have it start up enough at the start? It's clear that Facebook wasn't using a single Apache/mod_wsgi process because that wouldn't get close to 2,000 requests per second. I'm sure they gave it the number of processes that were approp…
Bret, quick question. Does the framework support an esi type tags to abstract out personalized info? thanks!
I am not sure what esi type tags are. Mind sending me a link? Suffices to say, no, we do not support that :)
It seems like this would not be mandatory in Tornado, since it is an app server; from my reading I'm assuming all pages are dynamic.
Bret, quick question. Does the framework support an esi type tags to abstract out personalized info? thanks!
I am not sure what esi type tags are. Mind sending me a link? Suffices to say, no, we do not support that :)
ESI: http://www.akamai.com/html/support/esi.html
e.g. When you and I log into ff, simplifying greatly, that page would say, "Welcome, Bret" or "Welcome, Prakash". If you could abstract away "Bret" and "Prakash", that page would be cacheable. And, the db hit is only for that particular fragment.
You would need to re-code the pages with esi tags to do it. The other way would be to use javascript to do the same.
What do you think?
A few notes: - template.py: "Error-reporting is currently... uh, interesting." - url mapping looks primitive - no form helpers - database.py looks decent, but is mysql only - Very nice to see the security considerations in signed cookies, auth, csrf protection.
Overall, it looks like they've done the trickier parts of building a web framework and left it to the user/community to add the parts web developers use most frequently (form & url helpers, code organization, and orm).
I love Facebook's enlightened approach to open source. If only one of their open source projects takes off, it will benefit them tremendously.
What exactly does 'non-blocking' mean in the context of a webserver?
What exactly does 'non-blocking' mean in the context of a webserver?
This is great. Any idea if they will do the same for the FriendFeed datastore?
This is great. Any idea if they will do the same for the FriendFeed datastore?