Clearer way to pass addresses as data over TCP Messengers
Issue #32
resolved
Current way of using Reply Message is easy to forget, Better if there was an Address-Message or API to make it easier to discover.
Comments (2)
-
-
reporter
- changed status to resolved
OK, not that I have a good idea of what to do. Close as no change.
- Log in to comment
As a note, we use TCP Messages for cross-network comms and simply store the reply address from within the first registration message in a dedicated VAT (1-to-n system). For our perspective, there’s no issue here with needing to improve the API.