WSGI protocol and its impact on the server, wsgi protocol server

WSGI protocol and its impact on the server, wsgi protocol server

The following content is my personal learning experience. If you have any questions about my point of view, please leave a message and I will learn from Daniel modestly.

 

The full name of WSGI is web service gateway interface. WSGI is a protocol specification that describes the communication between web service and web application, rather than a server, an API, or a module.

To implement the WSGI protocol, web service and web application must be implemented. Currently, the Protocol frameworks running on WSGI include FLASK, DJANGO, and TORANDO.

The WSGI protocol must contain two parts: web service and web application. The implementation principle of the client and server is as follows:

The WSGI application receives the request forwarded by the server, processes the request, and returns the processing result to the server. The application can contain multiple stack-based middleware (middlewares). These middleware must implement both server and application,

Therefore, it can be adjusted between the WSGI server and the WSGI application: for the server, middleware acts as the application, and for the application, middleware acts as the server.

As long as the web service and web application implement the WSGI protocol at the same time, different web services can be combined with the same web application to form a server, different web applications can be

Service is combined into a server.