Which problem did you have exactly?
This is not something to be integrated into the protocol, more like a workaround of the current limitations of the HTTP outcalls (with a big trade-off).
Improving the native HTTP outcalls would of course be amazing but we don’t have the resources to do it by ourselves now.
What we instead want to do is to deploy the off-chain client on a separate network which an orchestrator canister controls. Eventually, we are not the ones controlling the orchestrator, the HTTP proxy and off-chain client so that devs don’t have to trust us when using this service.
For a little more context, check this out. We will publish a more detailed explanation soon!