MystenLabs
Add support for separately configured address for own workers
- Sui contacting its own worker makes a lot of sense to me (prior art: MystenLabs/narwhal#715), but could you say more about the use case in which Narwhal itself would need access to this information?
This is for Narwhal primary to contact its own workers, just using a different address than a remote primary would use.
- Usual naming for addresses to the same logical machine centers around the adjectives "internal" rather than "own".
internal_worker_address?
The name "own" vs "others" is used in the narwhal codebase already (eg "own" vs "others" batch message types, and in the Committee struct "own" vs "others" for workers and primaries). So I chose this name to stay consistent.
The name "own" vs "others" is used in the narwhal codebase already (eg "own" vs "others" batch message types, and in the Committee struct "own" vs "others" for workers and primaries). So I chose this name to stay consistent.
@aschran the worker_address that sits right next to the own_worker_address which you're introducing is also the primary's own worker's address, albeit its public one. I think we're reaching for a distinct qualifier here.
