When spawning processes via the Timecraft runtime API, it's now possible to spawn a sidecar process that proxies outbound traffic. For example, you can use the sidecar to change/reject HTTP requests on the way out, and change HTTP responses on the way back in. You could also implement request coalescing / caching / authentication / etc at this layer. This complements the sandboxing capabilities of Timecraft, allowing you to build privileged middleware that's hidden from an untrusted process.
When spawning processes via the Timecraft runtime API, it's now possible to spawn a sidecar process that proxies outbound traffic. For example, you can use the sidecar to change/reject HTTP requests on the way out, and change HTTP responses on the way back in. You could also implement request coalescing / caching / authentication / etc at this layer. This complements the sandboxing capabilities of Timecraft, allowing you to build privileged middleware that's hidden from an untrusted process.