Introduction CYFS for Developers(Part4): Services

[streetycat]

Introduction to CYFS Developers(Part4): Services

I want to introduce the services in CYFS in this issue.

Devices

As introduced here, there are 2 types of devices in CYFS for users and developers. They are OOD(gateway) and runtime.The relationship is as follow:

Zone A			<-->	Zone Other
runtime A1	<-->	OOD(gateway) A		OOD(gateway) O	<-->	runtime O1
runtime A2	<-->				<-->	runtime O2
runtime ...	<-->				<-->	runtime ...
runtime An	<-->

Services

In a zone, several services is running on the OOD always. These services are running depend on the gateway, the gateway is also a service, It is equivalent to nginx for http, receive and forward the requests to the target services.

gateway	<-->	app-manager
	<-->	chunk-manager
	<-->	file-manager
	<-->	...

1. app-manager: It manages the DecApps running on CYFS, install,uninstall,update,start,restart,stop,deamon.
2. chunk-manager: The chunk-manager binary is the first experimental NDN implementation (completed in April 2020), which is quite different from the current NDN implementation. Currently this component is only used for Service and DecApp package download.
3. file-manager: Similar to chunk-manager, it is the first experimental NON implementation (completed in March 2020), and is currently only used for Service and DecApp package downloads.
4. ood-deamon: It will restart the gateway when the process is dead. It is an independent service that does not depend on gateway.
5. ood-control: It is not a standalone binary service and is used by programs like ood-daemon or ood-installer. The purpose is to complete stack activation-related functions via the http interface.

DECApp

By the way, the server of a DECApp is also running as the services on OOD. They listen to requests from clients through the gateway and respond.

Thanks @weiqiushi for the correction

[weiqiushi]

chunk-manager: The chunk-manager binary is the first experimental NDN implementation (completed in April 2020), which is quite different from the current NDN implementation. Currently this component is only used for Service and DecApp package download
file-manager: Similar to chunk-manager, it is the first experimental NON implementation (completed in March 2020), and is currently only used for Service and DecApp package downloads.
ood-control: It is not a standalone binary service and is used by programs like ood-daemon or ood-installer. The purpose is to complete stack activation-related functions via the http interface

[streetycat]

chunk-manager: The chunk-manager binary is the first experimental NDN implementation (completed in April 2020), which is quite different from the current NDN implementation. Currently this component is only used for Service and DecApp package download file-manager: Similar to chunk-manager, it is the first experimental NON implementation (completed in March 2020), and is currently only used for Service and DecApp package downloads. ood-control: It is not a standalone binary service and is used by programs like ood-daemon or ood-installer. The purpose is to complete stack activation-related functions via the http interface

Thank you, but the module names are very confusing with the current implementation，will it update in future?