Hi guys, I have some questions on the procedures to update dependent resources.
Suppose the network map M updates from v1 to v2; in the meantime, four cost maps C1 C2 C3 and C4 that depends on said network map each have their own update and they switched dependency from networkmap v1 to networkmap v2. What is the process of updating these 5 resources/applying these updates if they become available at different times? Our main goal is for the update to happen as soon as possible and for all the involved resources to remain as available as possible. Theoretically, similar to what a compiler/linker does, since the cost maps depend on M, we should update M first to v2, then update the depending resources. The issue with this approach is that until all cost maps are updated, their look-ups are potentially not usable as their dependent network map has changed. If we hold off applying the update on network map, we must wait for all depending resources to complete. That's not ideal either. Should the clients store multiple versions of resources then? How would this work? Are there examples from other implementations that handle similar questions (e.g. compilers, git internals, software package updates, etc.)? Thoughts? Cheers, Xiao
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
