Not everybody is so enthusiastic about a web framework like tornado. There are two ways tornado achieves its speed:
1) uses multiple processors (this is a nice feature that we should take advantage of. Right now the only option is to use a load balancer and one server per processor) 2) It is asynchronous. That is what all the buzz is about but we proved we can achieve the same speed with a normal multi-threaded web server (the benchmarks are in the docstrings of the gluon/sneaky.py file). The tornado implementation is not portable and runs only on linux. What is most important is that by being asynchronous, requests are received concurrently computation is done sequentially sequentially. This is good only if you know each request is fast (like print hello world). A request that is complex (like a complex db query or a minor computation) would cause every other request to wait. This is not a good concurrency model for application that can be complex. On Dec 6, 7:41 am, Pystar <aitoehi...@gmail.com> wrote: > I have been going through the tornadoweb framework, the framework > that power's the realtime friendfeed website. I find it very > interesting and was wondering if that "realtime" characteristic of the > framework can be implemented in web2py? I feel it will really give > web2py a niche in the array of python web frameworks. > Thanks > Pystar -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
