From 72a02841fe98e8247335d486f2fede11110f0575 Mon Sep 17 00:00:00 2001 From: Sascha Ohms Date: Tue, 14 Nov 2023 20:13:31 +0100 Subject: [PATCH] docs: fix link to Rotom repository --- pages/docs/rotom/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/docs/rotom/index.mdx b/pages/docs/rotom/index.mdx index 5442b41..b680b06 100644 --- a/pages/docs/rotom/index.mdx +++ b/pages/docs/rotom/index.mdx @@ -1,6 +1,6 @@ # Rotom -[**Rotom**](https://github.com/UnownHash/Dragonite-Public) is our device controller. When a device connects to Rotom it will be registered as 1 to many workers creating a pool of workers that can process events. How many workers are available is dependent on your MITM provider and the configuration you provide within your MITM tool. You can think of Rotom as a task scheduler, Rotom will pull jobs that need to be processed from Dragonite (backend controller) and will send those request to various workers depending on time, available capacity, and configuration. +[**Rotom**](https://github.com/UnownHash/Rotom/) is our device controller. When a device connects to Rotom it will be registered as 1 to many workers creating a pool of workers that can process events. How many workers are available is dependent on your MITM provider and the configuration you provide within your MITM tool. You can think of Rotom as a task scheduler, Rotom will pull jobs that need to be processed from Dragonite (backend controller) and will send those request to various workers depending on time, available capacity, and configuration. Rotom communicates via websockets (`ws://`) to devices and Dragonite. This communication strategy allows for a smarter feedback loop between the backend server and actual worker.