Why can't we make web2py faster ? On Thursday, February 2, 2017 at 9:36:34 AM UTC-5, mcm wrote: > > > I agree nice and could be useful in speedy services and we should see if > it can be used in front of web2py. > > But it is more important for the long term that we start to think about > leveraging HTTP/2 soon > > Il giorno mercoledì 1 febbraio 2017 16:23:46 UTC+1, Anthony ha scritto: >> >> On Wednesday, February 1, 2017 at 4:54:31 AM UTC-5, Massimo Di Pierro >> wrote: >>> >>> I just discovered this: >>> >>> https://github.com/squeaky-pl/japronto >>> >>> I am impressed. I like the speed and the semantics. >>> >> >> Seems interesting, though the benchmarks seem a bit contrived. It does so >> well because it uses HTTP pipelining with a workload designed to get >> maximum benefit from pipelining (24 identical and fast pipelined requests >> requiring no work in Python). Since most browsers do not support HTTP >> pipelining by default, and most workloads would not benefit so much from >> pipelining, this has little real world value. On the other hand, it does >> *not >> *support HTTP/2 with request multiplexing, which *is *supported by most >> browsers and would likely have real benefits for more typical workloads. >> >> Regarding the API, how do you think it compares with Sanic >> <http://sanic.readthedocs.io/en/latest/index.html> (also based on uvloop >> and allowing async handlers)? >> >> Anthony >> >
-- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
