5,838
edits
Category:Cumulus MX: Difference between revisions
m
→Library software
| Line 641: | Line 641: | ||
= Library software = | = Library software = | ||
Cumulus MX uses '''library''' software (i.e. software written by others and made available by the provider and often also by other content delivery nodes or 'cdn') for a lot of the standard functionality. The library software | For most Cumulus users, this whole section can be skipped, but I have included it for those few users who have a technical slant and might want to understand more. | ||
Cumulus MX uses '''library''' software (i.e. software written by others and made available by the provider and often also by other content delivery nodes or 'cdn') for a lot of the standard functionality. The library software for the admin interface and the separate library software for the standard web pages are both mostly included in the distribution zip, although some is used via a link to a cdn. | |||
Many of the libraries included by MX are very obsolete. However, Mark Crossley, the current developer, said the following on 30 Sept 2019: | Many of the libraries included by MX are very obsolete. However, Mark Crossley, the current developer, said the following on 30 Sept 2019: | ||
| Line 647: | Line 649: | ||
Just to mention the other side of this balance. It is difficult to code an addition to MX that works with these obsolete versions of libraries. All documentation provided by providers of the libraries relates to current versions of the packages (and what is documented to work now often will not work with obsolete versions). The documentation for the packages that are no longer supported is only available in archive sites if available at all. | Just to mention the other side of this balance. It is difficult to code an addition to MX that works with these obsolete versions of libraries. All documentation provided by providers of the libraries relates to current versions of the packages (and what is documented to work now often will not work with obsolete versions). The documentation for the packages that are no longer supported is only available in archive sites if available at all. | ||
==Library Software for the MX engine== | |||
The distribution zip contains various '''.dll''' files and these are the libraries used by MX itself. | |||
===Devart=== | |||
The two files used are both related to the database functionality of MX. | |||
===FluentFTP=== | |||
As the name suggests, this is used by MX for controlling the file transfer functionality. This component has been updated at certain MX releases, see the announcements for details. | |||
===Linq=== | |||
Language INtegrated Query is used to work with sequences of items and pick the ones that are needed, putting them into output format required. MX uses two files in connection with preparing output for Twitter. There is a third Linq file for other processing. | |||
===MQTT=== | |||
When MX added capability to talk to other devices using the MQTT protocol, it added this component for that optional functionality. | |||
===Newtonsoft=== | |||
This component is used for processing JSON strings. It is a very popular choice for developers, and used therefore very widely. However, '''SystemText''' has superseded it, so MX is using an obsolete method. | |||
===Renci SSH=== | |||
This component is server connection software, it is what processes the host name, password, and so on. | |||
===SQLite3=== | |||
This is used for all interactions with the [[Weather Diary|weather diary]]. | |||
===HTTP=== | |||
These files handle the optional HTTP functionality. | |||
===Unosquare=== | |||
The EmbedIO file is open-source software that handles the web-sockets functionality of MX. The Swan file is open-source software that handles JSON formatting and threading of tasks in MX. | |||
== Library software for admin interface == | == Library software for admin interface == | ||