rtyler
/
brokenco.de
1
0
Fork 0
Code Pull Requests Releases Activity

Update the control port decision in the blog post

This commit is contained in:
R Tyler Croy 2020-10-29 20:34:18 -07:00
parent b45ccf859a
commit 4ac7c53b81
No known key found for this signature in database
GPG Key ID: E5C92681BEF6CEA2
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
_posts/2020-10-22-smalltalk-inspiring-otto.md
View File

@ -29,6 +29,15 @@ communicate with that protocol. My first thought was just lines of JSON encoded
over the wire, but there are a number of practical problems with trying to send
JSON over a unix socket, for example.
---
**Update 2020-10-30**: I have since decided to shy away from Nanomsg for the
control socket and instead have opted for a small HTTP server listening on a
unix socket. I chose this approach to make the debugging and client
interactions much easier, even a totally bash-based shell step would be able to
interact with it!
---
For the first implementation, I am planning to have a single long-lived socket
for the duration of a pipeline's execution by the agent. By adding the `ipc`
field to the invocation file (below), I should have the flexibility to allow an