I will answer the above points(#1,#2).
Please refer to attached document.

Below are the consolidated feedback discussed in the F2F Meeting at San Jose on 12th July 2017.

(TMC/Mentor to respond to these points one by one in the fore coming days.)

1. Security Vulnerability: The registerApplication() method that has the application-id as parameter represents a security vulnerability. Window Manager needs to consider the session capability from the ApplicationFramework and previously obtain the ApplicationID from the AppFramework. Basically clients shall not send application-id to the Window Manager.

2. Performance: A lot of communication back and forth between the WindowManager and the Applications. This is related to the drawing synchronization and the notifications for visibility and focus.

3. Multi-Display-Support:-Expansion: About Window Manager supporting multiple displays on multiple ECU’s in future, There are some companies currently interested in adding this support on AGL platform. Maybe Mentor needs to reconsider and add some support for this feature in the API. Even if this feature is not implemented now, it should be considered in the window manager architecture and the API needs to be designed to have scope for expansion in the future.

4. Pop-up: A separate NotificationManager need to be added to allow the applications to have the popups instantly displayed. Will Pop-up timeout specified by OEM or by Application?

5. QML Support: Who will implement QML Client and when?

      6. SMACK level checking and verification need to be performed