How out of process services work in clank and Android WebView?

[Hazem Ashmawy]

Hello there,

This is Hazem from the WebView team. I want to reuse components/services/unzip in a non-embedded WebView process.

Nonembedded WebView is when WebView runs outside of apps as it's own standalone app. It doesn't initialize a browser context and can't depend on //content/. So it can't use the recommended out-of-process service launching similar to what is done here.

We want to launch the service in-process similar to here. However, it's limited to IOS and tests only for security concerns.

To assess these concerns, I wanted to know how the out-of-process services work in chrome on android in general? Does it actually launch a new process? or it funnels it to the same chrome process under the hood?

I am also curious to know how it works in Android WebView which is embedded inside other apps?

Thanks,

[John Abd-El-Malek]

Clank doesn't run network service out of process due to memory constraints. It does run some short lived services out of process for security reasons. WebView never runs network service out of process as well for the same reason.

Services built on top of mojo allow the code to abstract which process the code runs in, e.g. it could be out of process or in process depending on device characteristics. As you note, a lot of this machinery depends on content.

It sounds like you just want to run the unzip code directly, e.g. skip the unzip abstraction layer, and call directly into zip::UnzipWithFilterAndWriters like what components/services/unzip/unzipper_impl.cc does.

--
You received this message because you are subscribed to the Google Groups "services-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to services-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/services-dev/CAJJNMuYpJ1XkYnXhKYFQu2CMVdZ0XgQ_B4Db5oMtkF6SVhbhPQ%40mail.gmail.com.