Provide an alternate transport mechanism

[chowey]

How would you recommend using an alternate transport mechanism (not TCP) for a request? Specifically, I want to pipe the HTTP request to another process using Windows named pipes.

I've been looking through the source code of CEF and I'll admit I'm a bit lost. I can trace the network request back to some "net::" objects which would bring me somewhere into the bowels of Chromium itself. Is that where I would ultimately need to go for such a thing?

I can use a "CefRequestHandler" to create a custom "CefResourceHandler", and then do the IPC using named pipes at that point. But the data is not HTTP. It works best for me to send the request as HTTP, and receive the request as HTTP. Is there some other option here to parse the "CefRequest" by hand?

[magreenblatt]

If you implement an HTTP or WebSockets server in your separate process you can communicate with that process directly via JavaScript or use CefURLRequest from C++ code. Try googling "embedded http server" for some ideas.

[chowey]

I was deliberately trying to avoid network sockets since they were giving me firewall problems on my target deployment systems. Definitely that is the simpler way to go since it all just works out of the box.