Instead of forcing to use Chromium's built-in network stack add the option to use QNetworkAccessManager like QtWebKit did or a similar mechanism.

Ideas:

1. Provide a abstract base class of a WebEngine NetworkAccessManager which can be subclasses and set on the QtWebEnginge instance. This base class uses Chromium's network stack as fallback by default.
2. Support QNetworkAccessmanager directly to ease the transition from QtWebkit to QtWebEnginge

IMO this feature is very important. Imagine an application setup which displays website. But these website cannot be accessed via HTTP but via a custom socket for example, etc.