Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!rt.uk.eu.org!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Return-Path: <python-python-list@m.gmane.org>
X-Original-To: python-list@python.org
Delivered-To: python-list@mail.python.org
X-Spam-Status: OK 0.003
X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'output': 0.05; 'http': 0.09; 'parsed': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; '(python)': 0.16; 'concurrent': 0.16; 'investigate': 0.16; 'justin': 0.16; 'received:80.91.229.3': 0.16; 'received:dip0.t-ipconnect.de': 0.16; 'received:plane.gmane.org': 0.16; 'received:t-ipconnect.de': 0.16; 'subject:user': 0.16; 'threads.': 0.16; 'all,': 0.19; '(in': 0.22; 'header:User- Agent:1': 0.23; 'question': 0.24; 'header:X-Complaints-To:1': 0.27; '(which': 0.31; 'gives': 0.31; 'writes:': 0.31; 'there.': 0.32; '"the': 0.34; 'knowledge': 0.35; 'but': 0.35; 'there': 0.35; 'belong': 0.36; 'charset:us-ascii': 0.36; 'too': 0.37; 'to:addr :python-list': 0.38; 'realize': 0.39; 'to:addr:python.org': 0.39; 'received:org': 0.40; 'first': 0.61; 'received:217': 0.63; 'skip:n 10': 0.64; 'more': 0.64; 'different': 0.65; 'details': 0.65; 'believe': 0.68
X-Injected-Via-Gmane: http://gmane.org/
To: python-list@python.org
From: dieter <dieter@handshake.de>
Subject: Re: AMQP listening and user-facing daemon
Date: Tue, 09 Jul 2013 09:05:19 +0200
References: <51D9E463.7030403@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Gmane-NNTP-Posting-Host: pd9e0a14d.dip0.t-ipconnect.de
User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.4.22 (linux)
Cancel-Lock: sha1:bBp68enL4I/KNRyGXCzPWU0qn3U=
X-BeenThere: python-list@python.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe: <http://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive: <http://mail.python.org/pipermail/python-list/>
List-Post: <mailto:python-list@python.org>
List-Help: <mailto:python-list-request@python.org?subject=help>
List-Subscribe: <http://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups: comp.lang.python
Message-ID: <mailman.4430.1373353533.3114.python-list@python.org>
Lines: 23
NNTP-Posting-Host: 2001:888:2000:d::a6
X-Trace: 1373353533 news.xs4all.nl 15872 [2001:888:2000:d::a6]:38241
X-Complaints-To: abuse@xs4all.nl
Xref: csiph.com comp.lang.python:50215

Justin Chiu <c.justin88@gmail.com> writes:

> What is the best approach to writing a concurrent daemon that can
> execute callbacks for different types of events (AMQP messages, parsed
> output of a subprocess, HTTP requests)?

I fear your question is too specific (which means you must investigate
yourself).

First of all, it is always very difficult to answer questions
like "the best way" -- many many details are involved there.

You provided details but to appreciate them one has to know
"AMQP", "Openstack Notifications", "twisted", "greenlets", ...
There will not be a lot of people with this knowledge (I do not
belong to them).


I believe that you will be able to realize a solution
based on (Python) threads. It gives you the more freedom
than "twisted" or "greenlets". But a different approach
might be "better" (in some respect).