Go to file
openharmony_ci a465e1e7e1
!217 部件化整改,修改帐号部件名,去除_standard后缀
Merge pull request !217 from 张阿龙/master
2022-05-06 08:09:42 +00:00
etc update etc/init/BUILD.gn. 2022-03-15 11:48:12 +00:00
figures update readme 2022-02-25 09:48:55 +08:00
sa_profile add dms 2021-06-17 13:10:47 +08:00
services/dtbschedmgr change os_account_standard to os_account 2022-05-05 16:04:18 +08:00
utils/native/include remove zuri from dmsfwk 2022-03-21 14:34:24 +08:00
.gitattributes update OpenHarmony 2.0 Canary 2021-06-02 02:21:10 +08:00
bundle.json remove zuri from dmsfwk 2022-03-21 14:34:24 +08:00
dmsfwk.gni fix json exception bug 2022-04-21 14:10:32 +08:00
LICENSE update OpenHarmony 2.0 Canary 2021-06-02 02:21:10 +08:00
OAT.xml sync code to master 2021-12-21 23:26:50 -08:00
README_zh.md update readme 2022-02-25 09:48:55 +08:00
README.md update readme 2022-02-25 09:48:55 +08:00

Distributed Scheduler

Introduction

Distributed Scheduler is used for cross-device component management. It allows the local device to access or control remote components, and enables app collaboration in distributed scenarios. Its main functions are as follows:

  • Remote ability startup: Starts an ability on a remote device.
  • Remote ability migration: Migrates an ability to a remote device.
  • Remote ability binding: Binds an ability on a remote device.

System Architecture

Figure 1 Distributed Scheduler architecture

Directory Structure

/foundation/distributedschedule
├── dmsfwk                      # DMS framework (DMS is short for Distributed Manager Service, also called the Distributed Scheduler Service)
├── dms_fwk_lite                # Lightweight DMS framework

Repositories Involved

Distributed Scheduler

distributedschedule_dms_fwk

distributedschedule_dms_fwk_lite