Difference between revisions of "NROD Message Batching"
Jump to navigation
Jump to search
PeterHicks (talk | contribs) (Added a page explaining message batching) |
m (Categorisation) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
Messages such as TD berth steps are high-volume, with messages rates reaching over 60 messages per second during peak periods. To ensure these messages are sent efficiently, they are batched in to a JSON list in groups of a maximum of 32 messages, and sent a maximum of every 5 seconds. | Messages such as TD berth steps are high-volume, with messages rates reaching over 60 messages per second during peak periods. To ensure these messages are sent efficiently, they are batched in to a JSON list in groups of a maximum of 32 messages, and sent a maximum of every 5 seconds. | ||
| Line 6: | Line 4: | ||
If no messages are to be sent in a 5-second period, then no message will be generated. | If no messages are to be sent in a 5-second period, then no message will be generated. | ||
| + | |||
| + | [[Category:Network Rail Data Feeds]] | ||
Latest revision as of 08:54, 20 May 2013
Messages such as TD berth steps are high-volume, with messages rates reaching over 60 messages per second during peak periods. To ensure these messages are sent efficiently, they are batched in to a JSON list in groups of a maximum of 32 messages, and sent a maximum of every 5 seconds.
In the worst case scenario, a message will be delayed for just under 5 seconds in a quiet period.
If no messages are to be sent in a 5-second period, then no message will be generated.
