[Service] wasm caching in built-in service 64/230764/23
authorDongHyun Song <dh81.song@samsung.com>
Tue, 14 Apr 2020 06:22:09 +0000 (15:22 +0900)
committerDongHyun Song <dh81.song@samsung.com>
Thu, 21 May 2020 06:14:13 +0000 (06:14 +0000)
commit89630a5e1f1c52c8ca755c5014058fc58a68c453
treebfc2b4e017692643cd2095dbdae6a5a553483d3c
parenteba0e42828c3d975b8df8d5209c92072f943b4af
[Service] wasm caching in built-in service

This will be a service application working as build WASM caching on
installation time.
Actual implementation will be developed by WASM part.

** WASM caching **

Regarding the performance of creating wasm cache on first loading
time, this patch will take the time on installation time to service
application side.
Service application is first launched while its installation time
by ContentServiceManager of TV component, then it is able to create
wasm cache ahead of UI application run.

However, if a user try to launch the app as soon as it is installed,
this wasm caching is ineffective or raising performance loss by
racing simultaneous generation of cache files.
This is important design point to consider.

Related chromium-efl patch:
  https://review.tizen.org/gerrit/230786/

Change-Id: I9b8c1630ddf22036f4dd98bbe1f962443e589a3f
Signed-off-by: DongHyun Song <dh81.song@samsung.com>
wrt_app/service/builtins/wasm_builder.js [new file with mode: 0644]
wrt_app/service/main.js