How to support custom schemes dynamic?

[Streamlet]

So far as I known, application must call CefSchemeRegistrar::AddCustomScheme in CefApp::OnRegisterCustomSchemes to register a custom sheme to set options.
It is OK for static schemes. "static" means when we write the code we already known what schemes to register.
In my case, I am writeing a webbrowser control using CEF, and I need to exposing an API to users to register custom schemes after browser process created.
CefApp::OnRegisterCustomSchemes is called on CefInitialize, that is too early for me. My walkaround is delay the creating of browser process and pass a command line swich like "--schemes=scheme1,sheme2".
Could you please provide a better mechanism for us?

Additionally, I am puzzled why we need to call CefSchemeRegistrar::AddCustomScheme on each process, including gpu process and utility process?
Would you please wrapper it inside CEF?

[magreenblatt]

Could you please provide a better mechanism for us?

Unfortunately not, as this early registration is a Chromium architectural requirement.

Additionally, I am puzzled why we need to call CefSchemeRegistrar::AddCustomScheme on each process, including gpu process and utility process?
Would you please wrapper it inside CEF?

Why is this a problem for you?

[Streamlet]

Could you please provide a better mechanism for us?

Unfortunately not, as this early registration is a Chromium architectural requirement.

Thank you for reply. I understand that very well.

[Streamlet]

Additionally, I am puzzled why we need to call CefSchemeRegistrar::AddCustomScheme on each process, including gpu process and utility process?
Would you please wrapper it inside CEF?

Why is this a problem for you?

Because the browser process got info about custom scheme from app.
Then I need to pass it to other processes through command line, as the early registration requirement.
Not so convenient for use. I think it might be better that CEF treats the custom scheme as its own resoponsibility and does all what needed.
Well, it is not a very big problem, only a litter litter litter inconvenient. ^_^

[magreenblatt]

In most cases the list of custom schemes is static (doesn’t change for a given application), so passing it dynamically in all cases would be wasteful.

[Streamlet]

OK. I see.