Hi Jens,
Sorry for the slow reply, I've been on leave.
In general, KJ async I/O objects are tied to the thread / event loop where
they were created. This means you cannot pass an AsyncIoStream between
threads. You can, however, pass a file descriptor. If you are careful, you
could tear down the
> On Nov 9, 2022, at 6:47 AM, 'Kenton Varda' via Cap'n Proto
> wrote:
>
> Have you tested whether your server is able to accept concurrent connections
> normally? E.g. if you open a connection with telnet or something without
> sending any bytes, leave that open, and then try to use your
Hi Jens,
Have you tested whether your server is able to accept concurrent
connections normally? E.g. if you open a connection with telnet or
something without sending any bytes, leave that open, and then try to use
your server, does it work?
What does your listen loop look like?
-Kenton
On
I’ve got a CapnP-based server program running on a Raspberry Pi 4. It’s written
in C++, using CapnP 0.9.1. It’s single-threaded; the main() function just sets
up a listener, calls kj::NEVER_DONE.wait, and stays there.
It works fine, except that every few weeks it stops accepting connections; it
