Unlike in other SDKs, there is no link between `RootContext` and `HttpContext` / `StreamContext`

[yskopets]

Summary

• Due to a missing link between RootContext and HttpContext, it's not possible to to apply to HttpContext configuration that was set in the RootContext during proxy_on_configure
• Why is HttpContext gets created by a standalone factory function rather than by RootContext ?

[mileswilson]

I'm also trying to understand how to solve this problem, and pass configuration to my HttpContext.

[dgn]

I just wasted a bunch of time on this. If the callbacks would accept closures with environment captures, this wouldn't be an issue

[bangau1]

I am also trying to reading configuration and pass it into HttpContext, but can't do that.
I notice that this article https://docs.eupraxia.io/docs/how-to-guides/deploy-rust-based-envoy-filter/ use forked version which basically let the RootContext create the HttpContext (so can inject the configuration to them). For now, I am using the article approach (the forked version)