Currently plane actively asks on each update tick trafficApi for info to check if destination still has good weather. This need to change - plane needs to receive notification of badWeather occurence so it does not need to ask for it
todo after common contract model get refactored into context models
split traffic api endpoint into ui intended and backend intended
calls directly between plane and airport - change backend host type to api host? (service discovery between planes and airports...) no - better add Rabbit and listeners in plane for bad weather event
Currently plane actively asks on each update tick trafficApi for info to check if destination still has good weather. This need to change - plane needs to receive notification of badWeather occurence so it does not need to ask for it