-
Task
-
Resolution: Won't Fix
-
Major
-
None
-
None
-
None
In SPEC-1645, I want to use appid between homescreen-service and applications. But there is a problem that application can not use “AFM_ID” to get appid itself. So we need think another solution how to imporve homescreen-service.
SPEC-1685
IMHO, AFM_ID or app name (or other various predefined value) should not use as indicator to identify receiver of event delivered in session between each app and homescreen service.
My proposal:
- HomeScreen Service should generate an indicator or use some unique value as it. Any value acceptable if it should be able to specify a properly receiver in all HomeScreen Service's clients and not be predefined.
- LibHomeScreen::subscribe() should retrieve an indicator from reply of "subscribe" returned by HomeScreen service.
- HomeScreenService send event 'TapShortcut' with properly indicator.
- LibHomeScreen::on_event() check the indicator.
Here is my thinking about it.
homescreen-service will contains three parts.
1 Interface module: Provide interfaces for other application.
2 applicationModel: Store applications information, for example, "application id", "communication indicator", "application status".
3 applicationManager: Receive requests, and process these request and send event to other applications. Right now, just showApplication request.
