| Änderungsprotokolle |
|---|
Im folgenden sind die letzten Änderungen der verschiedenen Softwarepakete aufgeführt.
Letze 10 30 100 1000 10000 Einträge
| Kategorie | Datum | Version | Eintrag |
|---|---|---|---|
| cego | 25.03.2026 | 2.54.21 | Improved checkpoint recovery. If crash occurs during checkpoint with enabled cpdump, the dump file is checked and if required, moved to ready state. This ensures a stable recovery also if a crash occurs after database xml is written and before the checkpoint dump file was moved to ready. |
| cego | 25.03.2026 | 2.54.21 | Version released |
| cego | 25.03.2026 | 2.54.21 | Cleanup work done for several encoding / decoding methods. Decoding constructors ( e.g. CegoSelect, CegoFactor, CegoTerm, etc ) have been reduced and for encoding, just the CegoProcBlock instance is needed ( for update query encoding inside procedures ) |
| cego | 22.03.2026 | 2.54.20 | Version released |
| cego | 22.03.2026 | 2.54.20 | small code cleanups |
| cego | 21.03.2026 | 2.54.19 | Version released |
| cego | 20.03.2026 | 2.54.19 | Improvement added to thread pool initialization ( db and admin ), if any network address cannot be bind, the daemon terminates immediately with error message ( introduction of init method to CeegoAdminThreadPool and CegoDbThreadPool ) |
| cego | 15.03.2026 | 2.54.18 | Version released |
| cego | 15.03.2026 | 2.54.18 | Improved exception handling for NETMNG_MAXSERCHAIN validation in CegoNet and CegoClient. In case of a validation, the connection on client side is closed in a controlled way with message "Fatal protocol error". Since there is no way to get more information from server side, this is ok.
On server side, in case of MAXSERCHAIN validation, the connection must be closed immediately ( also for security reasons ), since the serial protocol can not be reset or recovered In CegoDefs, NETMNG_MAXSERCHAIN has been increased to 4MB |
| cego | 14.03.2026 | 2.54.17 | Version released |