<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>UWSGI on Lin's Blog</title><link>https://coder.tw/en/tags/uwsgi/</link><description>Recent content in UWSGI on Lin's Blog</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 24 Jul 2015 19:17:45 +0000</lastBuildDate><atom:link href="https://coder.tw/en/tags/uwsgi/index.xml" rel="self" type="application/rss+xml"/><item><title>uWSGI</title><link>https://coder.tw/en/posts/uwsgi/</link><pubDate>Fri, 24 Jul 2015 19:17:45 +0000</pubDate><guid>https://coder.tw/en/posts/uwsgi/</guid><description>&lt;h1&gt;Introduction&lt;/h1&gt;
uWSGI is a protocol, and it is also a program.
&lt;p&gt;Why is it so complicated? Let&amp;rsquo;s start with the program. uWSGI was originally designed so that web applications written in Python could communicate with web servers such as Nginx and Apache. It uses its own uwsgi communication protocol. It also supports other protocols such as CGI, FastCGI, and sockets, so besides serving Python, it can also integrate with programming languages such as PHP and Go.&lt;/p&gt;</description></item></channel></rss>