Stale Message Safeguard
I don't really have a clear idea how you'd best design it, but some form of support for expiring message values after a defined time. For example: using pAcommsHandler, as is, the latest nav_x,nav_y pair would be taken from MOOS and tx'ed using goby. But that pair could have any age: it wouldn't be useful to send these values if they are, say, 2mins old. (I guess we kind of assume that these values are regularly produced at high frequency at present)
I imagine that this could be an extra field in the xml description:
<float>
</float>
I assume that you'd need a special value of the nav_x variable to indicate this value has expired or the message would not be created if any of the values are outside their expiration period.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Maurice Fallon
- Direction:
- Needs approval
- Assignee:
- toby schneider
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by