Broadcast Server - BCS
Component | Versions |
|---|---|
BCS.EXE BCSGUI.EXE BCS64.EXE BCSGUI64.EXE | 6.5.483.0 6.4.468.4 (patch) |
IMPORTANT HINT | In version 6.5 only 64-bit variants are available. 32-bit variants have been dropped. This includes the old/deprecated SeplProtocol, too. If you still run clients, which need to communicate via SeplProtocol with BCS, you have to use version 6.4. |
Dependencies
DigaSQL.dll 3.22.3520.0 or newer
DigaSQL64.dll 3.22.3520.0 or newer - for use with BCS64.exe
New/Changes/Fixed Issues
for 6.5.
New
New icon of BCS.
Changes
The 32-bit variant of BCS has been dropped. Only the 64-bit variant will be available in the future. As a consequence, the old SeplProtocol is no longer supported. Only WebSocket clients can connect to BCS.
If you still have very old clients, which need to use SeplProtocol, you have to first run an older BCS (recommended is Release version 6.4) until all clients have been updated to a recent version. (OIA-8242)
The default value for the parameter BroadcastServer\<config>\Settings\StartAttributeInheritance was changed from "Legacy" to "Regular". With "regular" inheritance, BCS inherits more start attributes from grouping nodes to the children than in "legacy" mode. This might affect older clients. All clients since version 6.1 from January 2023 are aware of this parameter and can act accordingly.
The change from version 6.1.432.0 to insert deleted nodes as last child into the day trash was not appreciated. Therefore, the old behaviour was reverted and the last deleted node is now inserted again as top child of the trash. (CCD-44690/OIA-6557)
Bugfixes
In generic broadcast messages an extra line break was appended behind the <<<<DATA>>>> separator of WebSocket messages. This could result in clients to no longer react correctly on these messages. This was a new bug since version 6.4.468.0. (OIA-8250)
When a full day, which contained at least one endpoint-story, was copied in DigAIRange onto another day, the nodes at the destination did no longer specify a date in the timestamps for Time_Start and Time_Stop. This could lead to consecutive errors and was a problem since version 6.1.432.0. (CCD-45691/OIA-8640)
for 6.4.
Changes
The change from version 6.1.432.0 to insert deleted nodes as last child into the day trash was not appreciated. Therefore, the old behaviour was reverted and the last deleted node is now inserted again as top child of the trash. (CCD-44690/OIA-6557)
Bugfixes
In generic broadcast messages an extra line break was appended behind the <<<<DATA>>>> separator of WebSocket messages. This could result in clients to no longer react correctly on these messages. This was a new bug since version 6.4.468.0. (OIA-8250)
For SeplProtocl clients, which requested the special notification types ExtendedTreeInfo" or "ExtraDeleteInfo" these notifications were not generated sometimes. (OIA-8250)
When a full day, which contained at least one endpoint-story, was copied in DigAIRange onto another day, the nodes at the destination did no longer specify a date in the timestamps for Time_Start and Time_Stop. This could lead to consecutive errors and was a problem since version 6.1.432.0. (CCD-45691/OIA-8640)