Hi all,
I am designing an application (in C++) where, upon invocation of a
particular RPC call, both the server and the client agree to cleanly
disconnect from one another. By "cleanly", I mean that both the server
and the client send a TCP FIN/ACK and nothing more (e.g. no RSTs).
Unfortunately, i
d if there's a TCP RST triggered under the
> > hood... since we're already killing the connection, we ignore that
> > error anyway.
> >
> > I suppose what we should do is, in the case that we receive a clean
> > EOF, inhibit the sending of an abort message ba
On Fri, 29 Sep 2023 11:26:05 -0500
Kenton Varda wrote:
> On Wed, Sep 27, 2023 at 4:37 PM 'Alex' via Cap'n Proto <
> capnproto@googlegroups.com> wrote:
>
> > 1. I would like to add a new RPC Message in rpc.capnp:
> >
> > goodbye @14 :Void;
>
st to simply allow the
> > > > rpcSystem to fall out of scope, at which point the destructors
> > > > can invoke the necessary machinery to send the GOODBYE and FIN
> > > > the TCP stream.
> > > >
> > > > What do you thi
