Some questions related to tornado httpserver and httpclient - Printable Version +- Python Forum (https://python-forum.io) +-- Forum: Python Coding (https://python-forum.io/forum-7.html) +--- Forum: Web Scraping & Web Development (https://python-forum.io/forum-13.html) +--- Thread: Some questions related to tornado httpserver and httpclient (/thread-976.html) |
Some questions related to tornado httpserver and httpclient - dullboy - Nov-17-2016 Question 1: tornado.httpserver is a non-blocking http server. Is there any blocking http server? Question 2: Does asynchronous always mean non-blocking? Does synchronous always mean blocking? Thanks for your help! RE: Some questions related to tornado httpserver and httpclient - micseydel - Nov-17-2016 Can you give some more context on these questions? The hello-world for tornado shows a synchronous example. As far as "any blocking http server" it depends on what you mean; do individual requests usually bock? Yes. Does the server itself run only a single blocking thread? No. From a bit of Googling, synchronous and blocking are largely synonymous with perhaps some nuance that I'm not getting. My background on this: I worked with Play Scala for a year professionally (it is heavy on "Non-blocking I/O"), and I've used Flask both professionally and many times for fun (it doesn't focus on "Non-blocking I/O" or anything like it). The biggest difference for my relatively simple purposes was that in Play, there was a lot of composition of futures. |