Hi All, Currently, xwalk runtime can run as service mode or non-service mode, e.g. when launching an application in service mode: ,---- | $ xwalk-launcher app_id `----
Or in non-service mode: ,---- | $ xwalk app_id `---- My question is that should we need to maintain these two ways in Crosswalk runtime model? I know that there are some advantages in service mode, such as lower memory consumption, better application life cycle management, easy to integrate with Tizen, etc. But it only supports Linux/Tizen platform, since it's based on DBus which is invalid (by default) in other platforms, like Windows and Mac OS X. For non-service mode, it can run in all platforms theoretically, but some features are not supported, e.g. onAlarm event, uninstall/update a running application, and I believe that more and more features will be based on service mode. Should we need to maintain these two modes or drop the non-service mode? Any comments? -- Best Regards, He, Xinchao _______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
