Handling tornadoes and asynchronous requests

My question has two parts:

  • What exactly does an “asynchronous server” usually called Tornado mean? Can someone provide a specific example to illustrate the concept / definition?

  • In the case of Tornado, what exactly does “non-blocking” mean? Is this due to the asynchronous nature of the above? In addition, I read it somewhere, it always uses one thread to process all requests, does this mean that requests are processed sequentially one after another or in parallel? If the latter is the case, how does a tornado do it?

+5
source share
2 answers
  • Tornado , - C10K. , - , , . Node.js Nginx . tornado.database, . Tornado IOLoop , . . .

  • Tornado, ; . Tornado , , -. Tornado.

, , HTTP-, Tornado () ( ), :

  • Tornado
  • , .

Tornado (, Django), 2 3 . Tornado IOLoop , Django ( -) , .

+10

web.py(cherrypy) . ? , ,

0

All Articles