Gateway-free, serial NDJSON transport for the Python SDK. Uses the same SDK handlers and protocol as HTTP; never starts Jetty or performs discovery. The owning process must select its own database before entering this loop.
Gateway-free, serial NDJSON transport for the Python SDK. Uses the same SDK handlers and protocol as HTTP; never starts Jetty or performs discovery. The owning process must select its own database before entering this loop.
(dispatch handler frame)Answer one SDK frame through handler as {:status :headers :content}.
:content holds the response bytes in base64. A route outside the SDK
audience, or a stream, answers status 400. The extension host door uses it too.
Answer one SDK `frame` through `handler` as `{:status :headers :content}`.
`:content` holds the response bytes in base64. A route outside the SDK
audience, or a stream, answers status 400. The extension host door uses it too.(serve! reader writer handler)Serve until stdin EOF. One response per request; results contain base64 bytes. Own the same View-to-session bridge as HTTP, so input/live Views are delivered to polling SDK clients. A timeout kills the owning process rather than reusing an ambiguously aligned pipe. Leaving this loop flushes and removes the bridge.
Serve until stdin EOF. One response per request; results contain base64 bytes. Own the same View-to-session bridge as HTTP, so input/live Views are delivered to polling SDK clients. A timeout kills the owning process rather than reusing an ambiguously aligned pipe. Leaving this loop flushes and removes the bridge.
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 |