[Feature] Resource Loader Architecture Design and Optimization for Distributed Web Engine about castanets HOT 10 OPEN

[yg48-jung commented Jan 18, 2018 ]
Content Modularization Project: Network Service
https://bugs.chromium.org/p/chromium/issues/detail?id=598073

from castanets.

from castanets.

[sunny-nam commented Jan 31, 2018]
I verified renderer-side resource loading is working with a NetworkService feature on 63 version.
But I couldn't access external websites such as google and naver with the feature.
I think the reason is a problem with proxy.

from castanets.

[VENU MADHAV MUSHAM added a comment Sep 7, 2018]
Initial CL to enable OOP Network Process https://review.tizen.org/gerrit/#/c/186954/
In Progress: Due to syncronization issue with network service, NavigationFail is triggered sometimes.
Move Network service funtionality to launch from RenderThread.

from castanets.

[VENU MADHAV MUSHAMadded a comment Sep 7, 2018]

• Initialize NavigationUrlLoaderNetworkService on RendererThread
  • currenly NavigationURLLoaderNetworkService(), NavigationURLLoaderNetworkService::URLLoaderRequestController() => Start(), OnComplete(), OnReceiveResponse() are initialized from BrowserThread::UI and BrowserThread::IO

• Handle callbacks of NavigationRequest and NavigationInterceptionCB in rendererer

from castanets.

Network Service Implementation [WIP] venumusham@976334c

from castanets.

Hi @nke94, just try to understand this issue. Please let me know if my understanding below is correct -
[1] Original chromium has browser process to manages all the renderers and the browser process controls all network accesses.
[2] In this distributed engine work, I guess that resource from device A is passed to device B directly at the rendering layer to get rendered, yet in device B the resource loader is still at the browser process.

I'm a bit confused. If statement in [2] is correct, how resource is passed from A DIRECTLY to device B's rendering layer?

from castanets.

Scenario: Browser running on device A, Renderer and Utility(Network Service) running on device B

• Browser initiates Main Resource request to Network Service, Network service - url loader loads main resource and notifies Browser, Browser forwards notification(CommitNavigation) to Renderer
• Renderer reads Main resource and creates DOM and sends CommitProvisionalLoad message to Browser.
• On Renderer, Document loader initiates sub resource (if any) request to Network service url loader directly and receives response

from castanets.

Network Service on Renderer - Implementation: #28

from castanets.

Thanks @venumusham!

from castanets.