Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement a virtual clock on the FlightContextFactory #19

Open
corstian opened this issue Oct 15, 2020 · 0 comments
Open

Implement a virtual clock on the FlightContextFactory #19

corstian opened this issue Oct 15, 2020 · 0 comments

Comments

@corstian
Copy link
Member

In order to properly dispose expired context instances to spare memory in long running processes, and properly fire triggers, bot in real-time situations as well as batch processing, we'd need a time stamp which identifies "current" time.

A major side effect is that we're unable to fire a completed event when an (arrival) theory has expired. This might happen in cases where an aircraft lands, and no further transponder messages are being received. The flight context will be discarded, and the theory will be discarded resulting in an incomplete flight record.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant