AddressSet & Route

[mrinalwadhwa]

I'm reading the ockam_core crate today and I'm curious to understand the thoughts behind AddressSet & Route being two separate types, since they have very similar shape. @spacekookie @thomcc

https://github.com/ockam-network/ockam/blob/dbe2ad601fd6dbea9afb6cc85b4ae68793acadef/implementations/rust/ockam/ockam_core/src/routing/address.rs#L12-L14

https://github.com/ockam-network/ockam/blob/ee0b384ddd3548ae53675e30c5b91bea17ed7753/implementations/rust/ockam/ockam_core/src/routing/route.rs#L8-L12

[SanjoDeundiak]

AdressSet is a set, e.g. worker can be registered using set of addresses and will be responding to messages received to any of them. Route is consequent list of Addresses

[mrinalwadhwa]

That makes a ton of sense, we should elaborate on that detail in docs.

[spacekookie]

Wondering if we could use a BTreeSet for the AddressSet internally actually. It would make address lookups a lot faster and make that distinction more clear

[SanjoDeundiak]

@spacekookie vector should be much faster considering we have less than 5 addresses at a time

[twittner]

ockam_node::Context also distinguishes the first address as primary and the rest as aliases.

[spacekookie]

Yea okay fair enough. I guess we're only rarely gonna have workers with lots more addresses