thrau / pymq Goto Github PK

DBus looks like a useful candidate as a pymq provider. There are several python bindings https://wiki.python.org/moin/DbusExamples

pub/sub needs to be solved somehow

The Redis provider sets channel prefixes to avoid collisions with other namespaces:

the AWS provider should to the same

See

create inverse to expose in pymq

• initate the bus (run will wait for subscriptions to appear)
• subscribe to something
• unsubscribe -> run loop will now return

expected behavior: run loop should wait for subscriptions to appear, unless close() was called

once pymq.init has been called, and a new process is created that also uses pymq, the child process is left with all the state of the parent process (including the runner thread that runs the command loop).

If the result of an rpc call is not collected (e.g., due to timeouts and late results), the result queue and its contents will remain in the redis instance indefinitely, potentially causing a memory leak.

A good fix would probably be to let the skeleton set EXPIRE with a sane default on the callback queue.

Instead of creating a new IPC message queue for each RPC call, we could attach an in-memory queue to the bus and have the stub method listen on that queue instead of a remote queue. Use the event loop to dispatch the correct event.

One could probably build an eventbus provider using posix message queues + some additional logic for pubsub.

enable asynchronous RPC via callbacks