Another way is for two (OS) processes to "pipe" I/O to each other.
The back-and-forth "protocol"? It could be as simple/ad-hoc vs. as formal/ceremonial as you prefer. It could be text line-oriented, or JSON, or s-expressions, or raw bytes. I might use this as a starting point, get some mileage, then decide if it's adequate or what to do instead. p.s. If you squint and abstract away certain details, this is similar to the HTTP service approach. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
