parse rpc replies and timeout if they're not on time

Not that it works though, demonstrated thanks to our attempts at
reusing a remote for a new client which is sending that version byte
before the rpc message. At least I think that's why.

Seems like send (to remote) is blocking and therefore the timeout
can't fire (same process). First things is that the timeout should
probably be in the server instead, in case the remote is blocking like
in this case. Second is that we'd at least seen something if the
server was calling the remote genserver instead of casting, du to
the default gen_server:call timeout of 5s.

Why are we casting in the first place? Well, we had to back when we
didn't collect the full rpc message before passing it on. That could
change now.

0 files changed, 0 insertions, 0 deletions