As of version 2.1.1 the HTTP interface and web server is implemented as a plugin. The 1.12 version (and some above) will still be available for a while. As a plugin, the web server runs in its own context, independent of the server. In this architecture, the web server doesn’t need to run on a server, although this will be the default, but can run on any system attached to the video network. On large systems with multiple servers, it might be best to run the web server on a separate system. The plugin is provided as a DLL and is managed by the manager service. The manager is installed as service on every server by default.
Connecting to user manager
The web server plugin logs in the same way as the client to a central user manager. This user manager is often the same as the management server (the master server) to which the system managed servers (client servers) connect to. In case of a system with only one server, this server is also the management server and the user manager. After the web server has logged in, it obtains all rights available for that user. For the web server this basically includes the right the see certain camera images from certainservers.
One connection for all images
When the web server is logged into the user manager, it is connected to all available servers. It is now able to transmit images from all those servers. A client only has to connect to one web server to obtain video in stead of connecting to every server separately.
To obtain video from a specific server, the server id must be supplied by the command. As can be seen in the Changelog by remarks for the 2.1.1 version, a lot of commands now have serverid added to their parameter list. If the server id is ommited, the serverid from the management server is taken.
All timestamps from version 2.1.1 are in UTC format.