In-process ITransport backed by a (fn [request-line] -> response-line).
No subprocess, but a FAITHFUL transport: it moves the same lines the subprocess moves, so a test that drives an addon through it is exercising the real wire rather than a stub of it. Two uses:
In-process ITransport backed by a (fn [request-line] -> response-line).
No subprocess, but a FAITHFUL transport: it moves the same lines the
subprocess moves, so a test that drives an addon through it is exercising the
real wire rather than a stub of it. Two uses:
- drive a kernel that is on this classpath, before it is compiled opaque,
so the same addon can be proven in-process and then shipped as a binary;
- inject a recording line function in a test, which is the only way to
assert the exact BYTES the proxy sends.(fn-transport line-fn)An ITransport whose -request! is line-fn, a (request-line -> response-line).
It answers nil before -start! and after -stop!, so a caller that skips the
lifecycle sees the same nil a dead pipe gives it.
An ITransport whose -request! is `line-fn`, a (request-line -> response-line). It answers nil before -start! and after -stop!, so a caller that skips the lifecycle sees the same nil a dead pipe gives it.
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |