Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>No complete answer, but:</p> <p>In your question, you're describing a <a href="http://en.wikipedia.org/wiki/Comet_(programming)" rel="nofollow noreferrer">Comet</a>-style architecture. Regarding support of Comet-style techniques in Python/WSGI, there is a <a href="https://stackoverflow.com/questions/960969/python-comet-server">StackOverflow question</a>, which talks about various Python servers with support for long-running requests a la Comet.</p> <p>Also interesting is this mail thread in the Python Web-SIG: <a href="http://mail.python.org/pipermail/web-sig/2008-July/003545.html" rel="nofollow noreferrer">"Could WSGI handle Asynchronous response?"</a>. In May 2008, there was a broad discussion in the Web-SIG about the topic of <a href="http://mail.python.org/pipermail/web-sig/2008-May/thread.html" rel="nofollow noreferrer">asynchronous requests in WSGI</a>.</p> <p>A recent development is <a href="http://code.google.com/p/evserver/" rel="nofollow noreferrer">evserver</a>, a lightweight WSGI server, which implements the <a href="http://mail.python.org/pipermail/web-sig/2008-May/003439.html" rel="nofollow noreferrer">Asynchronous WSGI extension</a> proposed by Christopher Stawarz in the Web-SIG in May 2008.</p> <p>Finally, the <a href="http://www.tornadoweb.org/" rel="nofollow noreferrer">Tornado web server</a> supports <a href="http://www.tornadoweb.org/documentation#non-blocking-asynchronous-requests" rel="nofollow noreferrer">non-blocking asynchronous requests</a>. It has a chat example application using long polling, which has similarities with your requirements.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload