<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>Asynchronous on Shaowen Chen's Website</title><link>https://www.chenshaowen.com/en/tags/asynchronous/</link><description>Recent content in Asynchronous on Shaowen Chen's Website</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>&amp;copy;2016 - {year}, All Rights Reserved.</copyright><lastBuildDate>Tue, 25 Oct 2016 07:57:59 +0000</lastBuildDate><sy:updatePeriod>weekly</sy:updatePeriod><atom:link href="https://www.chenshaowen.com/en/tags/asynchronous/atom.xml" rel="self" type="application/rss+xml"/><item><title>Using Celery in Django</title><link>https://www.chenshaowen.com/en/blog/using-celery-in-django.html</link><pubDate>Tue, 25 Oct 2016 07:57:59 +0000</pubDate><atom:modified>Tue, 25 Oct 2016 07:57:59 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/using-celery-in-django.html</guid><description>Scenario one: the company is preparing to push an email announcement to all employees. Using a wrapped mail library API and looping over every employee to push the emails will leave the main program stuck in the loop and unable to respond, which is not what we want — we want to be able to carry on with other operations normally after clicking execute.</description><dc:creator>WeChat Official Account</dc:creator><category>Celery</category><category>Django</category><category>Python</category><category>Asynchronous</category><category>R&amp;D</category></item></channel></rss>