The following pages and posts are tagged with
| Title | Type | Excerpt |
|---|---|---|
| Announcement | Page | Announcements are special signals which are published in order to announce something before it actually happens. For example, before an event is created and published, an announcement could signal that the event will happen soon. Announcements have the following characteristics: they are not persisted/appended into any data... |
| Command | Page | Commands involve the need to change or retrieve something of a digital twin managed by Ditto or an actual device connected to Ditto. Commands always contain an identifier of the entity they address (e.g. a Thing ID). Modify Commands Commands which modify a digital twin or an... |
| Command response | Page | CommandResponses are the answer to Commands and include information about whether the intention of changing something via a ModifyCommand has worked or if there was an Error instead. The CommandResponse of QueryCommands contains the requested information. |
| Error response | Page | If an issued command or message could not be applied, an appropriate error response conveys this error information back to the issuer. Failure of a command or message can have various reasons, starting from missing permissions to internal server errors during processing of the command. The... |
| Event | Page | Events report that something took place in a digital twin in Ditto. Important is the “past tense” here; it took already place (it was for example persisted into the data store) and cannot be reversed or stopped. Events are one of the centerpieces of Ditto: they are persisted/appended into... |
| Signals | Page | Ditto has a concept called Signal which combines common functionality of Commands, Command Responses, Error Responses, Events and Announcements. Such common functionality is for example that all those have header fields in which they can be for example correlated to each... |