Bug 2008

Summary: 1.[Helper API] Understand bitbake server build mechanism to implement bitbake server helper (rest API) for web UI
Product: [Build System, Metadata & Runtime] Hob Reporter: xiaotongx.lv <xiaotongx.lv>
Component: hobAssignee: xiaotongx.lv <xiaotongx.lv>
Status: VERIFIED INVALID QA Contact:
Severity: enhancement    
Priority: Low CC: dongxiao.xu, jessica.zhang, jiajun.xu, poky.bs.watcher, poky.watcher, sgw, shane.wang
Version: unspecified   
Target Milestone: 1.3   
Hardware: x86   
OS: Multiple   
Whiteboard: (P3)
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description xiaotongx.lv@intel.com 2012-02-19 17:33:16 UTC 
According to hob codes, if we run bitbake server via the way of RPC, I find there are 2 RPC server in the 2 sides, in the bitbake server, RPC server provide a interface to hob client and hob can sends the commands to tell bitbake what to do, then bitbake starts to do the thing and produce many events to register hob client RPC server for hob to handle and showing to UI.
So if my understanding is right.I will do some testing work to continue to know details, and then implement a helper for web server.
Comment 1 xiaotongx.lv@intel.com 2012-06-20 01:58:28 UTC 
Cancel the helper based on restful implementation, instead of webservice technology.
Comment 2 xiaotongx.lv@intel.com 2012-06-20 02:01:08 UTC 
remove this bug
Comment 3 xiaotongx.lv@intel.com 2012-06-20 02:02:56 UTC 
remove and cancel this bug