I've added a patch that solves my issue for future reference.
On Monday, October 18, 2021 at 7:44:30 AM UTC+2 Leon Wessels wrote:
> Thanks for the info. I'll look into it and post an update.
>
> On Saturday, October 16, 2021 at 6:31:21 AM UTC+2 tripl...@gmail.com
> wrote:
>
>> I'll try to poke
Thanks for the info. I'll look into it and post an update.
On Saturday, October 16, 2021 at 6:31:21 AM UTC+2 tripl...@gmail.com wrote:
> I'll try to poke at the code this weekend. But what you're trying to do
> "should" work.
>
> One thing I've noticed is that when things hang with Python
I'll try to poke at the code this weekend. But what you're trying to do
"should" work.
One thing I've noticed is that when things hang with Python asyncio it
usually means something is wrong with whatever is polling the tx on the
sending side or the rx on the receiving side. If anything died
Hi Leon,
Abstractly, what you describe should be easy with Cap'n Proto. One client
can send a capability (interface reference) to the server, and the server
can freely send that capability on to some other client. Cap'n Proto will
automatically arrange to proxy messages from one client to the
Hi,
I have a use case where multiple clients connect to a server. A call from a
client to the server might require the server to call another client. For
some functionality a direct call from one client to another would be best.
For performance reasons some clients will be written in C++. For
