Future: Write HTTP REST API "backend" specification

[jancurn]

Currently, the whitepaper describes a general web Actor programming model, but this is not sufficient to enable third-party implementations of the Actor system.

In particular, we'd need to define standardized low-level HTTP REST API interface to the Actor system, to separate "frontend" and "backend" Actor programming model implementations. For example, if somebody wants to build a support for Actor programming model in Rust, they should need to just write a Rust "frontend" translating the commands to HTTP API calls, rather than having to implement the entire system. And equally, if one decides to develop a new Actor "backend", all existing client libraries for Rust or other languages should work with it.

We should specify this interface (e.g. take inspiration from Docker engine), and ensure the Actor CLI, Apify SDK, and the Apify platform conform to that.

cc @tobice

[tobice]

As discussed on the last meeting, I'm reassigning this to @netmilk, the actual owner here.

[netmilk]

@tobice I hereby confirm the reception of your note and accept the ownership.