roslibrust
roslibrust copied to clipboard
Add support for parsing the remaining fields in the Connection Header
Currently missing a couple (see tcpros.rs), however I didn't see these in the packet capture coming from the subscriber node so they're documented but maybe unused in practice.
Note: through my various work on services a lot of fields were added, but things definitely look funky and the whole header could stand to get a once over. A lot of the fields are optional in different ways in different contexts, so we may want a PublisherAdvertiseHeader, and ServiceClientConnectHeader etc.