Apache vs Twisted

I know that Twisted is a structure that allows you to do asynchronous non-blocking I / O, but I still don't understand how this differs from what Apache does. If anyone could explain the need for twisting, I would appreciate it.

+4
source share
4 answers

Twisted is a platform for developing Internet applications, for processing basic communications, etc. He doesn’t do anything out of the box - you have to program it.

Apache is an online application. After installation, you have a working web server that can serve static and dynamic web pages. In addition, it can be expanded to do more than is possible.

+10
source

These are two different things, one is a clean WEB server, and one is a WEB infrastructure with integrated event-driven servers.

Twisted is good for building high-performance network network services.

+2
source

FYI, FriendFeed / Facebook just open their own server and framework: Tornado . Matt Heitzenroder of Apparatus conducted an initial comparative test, and looks like a “Tornado” left in the dust .

+2
source

@alphazero. You read that the Twisted vs. Test Tornado is wrong (or you haven’t read it at all). Quote from an article: "Less average response time is better." Twisted below. People want their web servers to respond with a lower (faster) time.

Twisted Tornado leaves in dust ... or, in fact, they differ by an almost trivial constant factor.

+2
source

All Articles