You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do the changes to the protocol in AQtion modify the information sent to the master? I did some preliminary testing and heartbeats/pings seemed to work as expected.
The protocol changes should not have affected how the information gets sent, but we did reduce the amount of data being sent (consolidated game modes into a single field for example, rather than a unique integer field for each type)
I toyed with the idea of validating all the key/value pairs that get sent in a heartbeat against the protocol but decided against it. As at the time it felt like a step that adds additional complexity while potentially locking out edge cases, and I'm going for broad compatibility at the moment. Current the master just grabs everything and stores it in DynamoDB as a JSON blob.
Test and confirm protocol 37 works as expected, or create a separate protocol definition for it.
https://github.com/tastyspleen/r1q2-archive
The text was updated successfully, but these errors were encountered: