Topic cluster
Other
Documentation not covered by the keyword groups shown in the parent cluster.
10 items
All documentation outside the keyword groups in the parent cluster is listed below.
cotonic.broker Cotonic
The broker module handles all local publish subscribe connections. The subscriptions are stored in a trie datastructure allowing quick action. They are available in the cotonic.broker namespace.
cotonic.mqtt Cotonic
The mqtt module provides functions to work with mqtt topics. The broker uses this module as the basis to provide its functionality. This module also has some utility functions to easily extract…
cotonic.mqtt_bridge Cotonic
This module makes it possible to bridge the broker on the local page to an external MQTT broker.
cotonic.tokenizer Cotonic
The tokenizer transforms text to html tokens. The tokenizer is used by the user interface composer in order to call the incremental-dom api. It uses incremental-dom to do in-place diffing of the…
cotonic.ui Cotonic
The user interface composer manages html snippets which can be placed in the DOM tree. When an updated html snippet is delivered to the composer it will render it by using Google's incremental-dom library.
model/lifecycle Cotonic
Application lifecycle is a key way that modern operating systems manage resources. On Android, iOS, and recent Windows versions, apps can be started and stopped at any time by the OS. This allows…
model/serviceWorker Cotonic
The serviceWorker model makes it possible to communicate with other tabs from the same site. This makes it possible to communicate important state to all tabs.
Page functions Cotonic
Cotonics main functions are available in the cotonic namespace on the main page. The functions are mostly used to control and allow messaging between workers.
Worker functions Cotonic
Workers are stand alone processes. They have no shared data with the page, nor with other workers. Their memory and calling context is isolated. They can easily communicate with other workers
Workers Cotonic
Cotonic uses Web Workers which all run in separate calling context. This means that they will not block the main user interface thread. They are also truly isolated from each other. This means…