Horace, I just reviewed the design doc. Here I provide my feedbacks to you about this document:
1) Page 5, line 9~13 What means that "no node is matched"? Does it mean that there is no desktop entry existed under proper folder or the entry file not recognized by Daemon? If so, why we support to start up such applications in Genesis? If an application has been executed, can I start up another instance for same application? 2) Page 5, line 14~16 How to monitor and handle the status of running applications and what are the reactions to the unexpected situation? Does any mechanism to update process id if a process was killed by user or by some exceptions? 3) Page 5, line 18~21 What are the expected actions if find applications (which is running) updated/uninstalled? 4) Page 5, 5.5 Unit Test Do you think of using some unit test framework, like "check", to wrapper all test cases and run them automatically? Thanks, Lei Y -----Original Message----- From: Li, Horace Sent: 2008年9月1日 23:48 To: [email protected] Subject: Application life-cycle manager design doc draft is attached. Hi, All, I completed a design document draft of application life-cycle manager, codename Genesis. Application life-cycle manager is part of application framework in Moblin 2.0 software stack, and you could find more detailed description in the document. Please help to review the document and see if the information included in the document is adequate and clear. Any comments are welcome. Application life-cycle manager project is currently available at http://test.moblin.org/projects/genesis-application-lifecycle-manager. Thanks, Horace _______________________________________________ dev mailing list [email protected] https://www.moblin.org/mailman/listinfo/dev
