Hi Stéphane,
On 14.11.2014 19:54, Stéphane Desneux wrote:
Hi Ilya,
TL;DR: preloading_preinitializing_daemon has been removed in Tizen 3
because the replacement of WRT by Crosswalk made it quite useless.
As I understood, WRT was the main use case for which
preloading_preinitializing_daemon had been created.
What about native applications? They also have a big number of libraries
they are linked to.
If preloading_preinitializing_daemon is removed, native application
startup time will suffer.
On the contrary of WRT where each web application was made of 2 (new)
processes to start, the crosswalk model is based on a main browser
process that forks applications => so preloading libraries is now useless.
But it's still useful for native applications, isn't it?
Also, the multiuser model introduced in Tizen 3 requires applications to
be launched inside different user sessions. As amd daemon runs as root
(or later as system user), we introduced the amd_session_agent which
runs inside each user session to fork/exec the applications with the
proper environment and security.
Does amd_session_agent does any library preloading (currently)?
Even if the amd_session_agent source code comes from the old preloading
daemon, they now are very different: preloading_preinitializing_daemon
is for Tizen 2.x only and amd_session_agent is for Tizen 3.x only.
Hope this clarifies a bit.
Best regards,
Ilya Palachev
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
