link流程 建立時需要注意的地方
Link-chain Framework
This framework is developed (as an example) so that it becomes easier for the individual modules to integrate themselves
with others, create a chain of different modules and test them together for a particular use case. It is based on few
assumptions and may not be suitable for all possible use cases.
A link is a stand-alone independent task which is created on top of a specific module (like capture, scalar, noise
filter etc) and is meant to perform a predefined operation. For e.g. the display link will only take care of the display
related functionalities, a noise-filter link will only look towards noise filtering etc.
A chain is a set of links joined together to perform a complete sequence of operations desired for the specific use
case. For e.g. capture and display links can be joined to form a chain which will capture frames from the input source
and display them on the connected output.
During initialization, each link registers itself with this framework and then creates its own individual task. This
task listens to the incoming messages and takes the appropriate actions.
Each link accepts messages from the previous link(s) (the only exception is capture link) and sends output to the
connected link(s) (an exception is display). The link is informed by its predecessor link once the data is available for
its use. The link can then start processing the data and once it is done, it informs the next link. The next connected
link in the chain will then start processing the data and the process continues.
1)System_linkCreate() API. Links MUST be created in the order of source link to sink link.
2)Next the chain is started by calling System_linkStart() for each link in the chain.The links are started in the order of sink link to source link. This is not a hard requirement but is usually desired in the application, since this allows all links to get ready to receive input before the source link itself is started.
3)After the user is done with a chain he can stop it by calling System_linkStop() API for each link of the chain.A chains MUST be stopped in the order of source to sink.
相關文章
- 使用Context建立一個View需要注意的地方ContextView
- delete與delete[]需要注意的地方delete
- 進行爬蟲的時候需要注意哪些地方?爬蟲
- Database Link 建立注意的兩點Database
- margin-top使用需要注意的地方
- /etc/fstab檔案需要注意的地方
- SharePoint 2016 安裝配置流程及需要注意的地方
- 用decode和nvl處理null值時需要注意的地方Null
- js switch語句需要特別注意的地方JS
- 26個提升java效能需要注意的地方Java
- Struts中上傳檔案需要注意的地方
- springMVC的@ResponseBody、@RequestBody使用需要注意的地方SpringMVC
- oracle over()的使用和需要特別注意的地方Oracle
- 使用rman建立standby db,資料檔案目錄結構不同需要注意的地方
- 【Redis】redis-cluster需要注意的幾個地方Redis
- javascript原型繼承constructor需要注意的地方JavaScript原型繼承Struct
- javascript變數宣告需要注意的一個地方JavaScript變數
- 在PHP中使用類可能需要注意的地方PHP
- java打包exe程式需要注意的幾個地方Java
- oracle 11.2.0.3 版本 vote盤需要注意的地方Oracle
- Database Link 建立注意的兩點【Blog 搬家】Database
- 行內元素和塊計元素需要注意的地方
- 伺服器搬遷需要注意的幾個地方伺服器
- visual studio建立專案時需要注意的問題
- 選擇雲伺服器有哪些需要注意的地方?伺服器
- 開發網路影片直播系統需要注意的地方
- hadoop中Combiner使用中需要注意的地方Hadoop
- 用Unity做個遊戲(一) - 建立專案時需要注意的點Unity遊戲
- 蘋果企業開發者賬號的使用需要注意哪些地方蘋果
- 箭頭函式適用場景及需要注意的地方函式
- Java基礎系列(三十六):泛型中需要注意的地方Java泛型
- 平臺接入美顏SDK工具有哪些需要注意的地方?
- PHP json_encode函式中需要注意的地方PHPJSON函式
- 對Oracle View授權和where查詢需要注意的地方OracleView
- jquery獲取ajax傳遞的值一個需要注意的地方jQuery
- 表連線時update與delete操作需注意的地方delete
- BigDecimal使用注意的地方Decimal
- 一個優秀的雲原生架構需要注意哪些地方架構