I noticed that when using the bytecode interpreter the request/response body was not always properly transmitted — a test will appear in a separate PR #222. This simplifies the client to not try to write things concurrently and changes both sides to shutdown the connection partially after being done with writing or reading. This seems to have eliminated the issue.
I noticed that when using the bytecode interpreter the request/response body was not always properly transmitted — a test will appear in a separate PR #222. This simplifies the client to not try to write things concurrently and changes both sides to shutdown the connection partially after being done with writing or reading. This seems to have eliminated the issue.