A lightweight multiple producer and single consumer IPC server that uses redis pubsub as a broker
Creates a redis ipc server that listens on a single pub/sub channel and allows you to communicate between multiple processes
Subclass the IPC class and add your handlers as methods
like this (handlers must start with handle_ as their name)
async def handle_channel_update(self, data):
return data
or use IPC.add_handler to add the handler after the
class has been instantiated
and whenever a process calls IPC.get, all the clients connected to
that channel will try to handle the request and whichever one finishes
first, will be returned by the function
the handler must either return a dict or None
None is treated as an implicit reason that the current
process doesn't matches the requests' target process
IPC.on_error handler for when a handler errors out. Takes error as first argument and message (the request data) as secondIPC.get and IPC.publishFAQs
A minimal multi producer single consumer IPC using redis pub/sub
We found that redis-ipc demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Malicious PyPI checkers validate stolen emails against TikTok and Instagram APIs, enabling targeted account attacks and dark web credential sales.
Security News
The Node.js TSC opted not to endorse a feature bounty program, citing concerns about incentives, governance, and project neutrality.
Research
Security News
A look at the top trends in how threat actors are weaponizing open source packages to deliver malware and persist across the software supply chain.