When your program is compatible with WSGI — which at the outer level means that the framework you are using has support for WSGI — your program can be deployed via any web server interface for which there are WSGI wrappers.
To sum it up: The Web server creates a listening socket and starts accepting new connections in a loop.
In my case I include a simple html script in the file named index. In fact it really is, and now it is time to explain it. That's because a web server is just a program, and can do whatever it wants when it gets a request: send back the file named in the previous request, serve up a Wikipedia page chosen at random, or whatever else we program it to.
For example, if we're using a search engine, we have to specify what our search terms are. You need to take off that last brick. This is the data that will be displayed and modified.
In order to make this tutorial a bit more illustrative of what one can do with the socket module, we will forego that part of the server and instead show how one can nuance the presentation of data. Google's mail service, for example, did not initially run on the common port numbers but, because they know how to access their accounts, users can still get their mail.
There is quite a bit of middleware already available. Hello, Web We're now ready to write our first simple web server.