
Changes in Dad 1.20 since 1.10
- A new function
dadMulMsg which allows to wait for
information on multiple sockets.
- Another new function
dadRepUpdate to overwrite old
information with timestamps in a given period of time.
- Two functions
dadNextUpdate and
dadPrevUpdate which return
time information at which the current updated dataflow looses
validity.
-
dadWUpdate is now documented to
set the iTimeEnd flag to
TIM_TILLEVER.
-
Servers now use
3 files for running. This is the real RZ file,
a backup of the state at server startup and a journal file which
a server can use to recover from backup.
Suppose the RZ file connected
to a served dataflow. This means a server crash does no longer
mean loss of data!
-
Stale unix sockets are detected at startup and automaticly removed.
- A bugfix in dadInit which could not
read in the k flag for keytable access, introduced in
Version 1.10. Also empty lines are now allowed in dadinit.cnf.
- A bugfix in dadAcceptSelect
which crashed the server.
- Removed asserts from the server code to let a server stay alive
even if the client sends garbage.
- CAC_GENTABLES can now be used even
if the table exists already. A projection is generated if needed.
- Various checks on the servers ddl are performed at startup
time to prevent at least some of the possible user errors.
- Fixed a severe bug that crashed the client if
CAC_KEYTABLE was used. Thanx to
Machiel.
Incompatibilies
Clients from 1.20 can no longer communicate to servers before
1.20. The server will complain about an unknown function if
the updating mechanism is used.
This page is maintained by Wolfgang Wander.