Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #50215 > unrolled thread

Re: AMQP listening and user-facing daemon

Started bydieter <dieter@handshake.de>
First post2013-07-09 09:05 +0200
Last post2013-07-09 09:05 +0200
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: AMQP listening and user-facing daemon dieter <dieter@handshake.de> - 2013-07-09 09:05 +0200

#50215 — Re: AMQP listening and user-facing daemon

Fromdieter <dieter@handshake.de>
Date2013-07-09 09:05 +0200
SubjectRe: AMQP listening and user-facing daemon
Message-ID<mailman.4430.1373353533.3114.python-list@python.org>
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).

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web