To detect if a train has gone and is no longer visible, there is a property LastModified. If times between ESTWs are not exactly synchronized, there can be a gap in the times. This leads to unexpected behaviour, e.g. trains disappear from Leibit although they are still in the simulation.
The detection if a train is gone needs to be reworked.
The LastModified timestamp needs to be persisted per ESTW because the times can differ.
It should not be the task of the client to detect if a train is gone. This logic should be implemented in the BLL.
To detect if a train has gone and is no longer visible, there is a property LastModified. If times between ESTWs are not exactly synchronized, there can be a gap in the times. This leads to unexpected behaviour, e.g. trains disappear from Leibit although they are still in the simulation.
The detection if a train is gone needs to be reworked.