Created
May 18, 2017 17:12
-
-
Save mkubarycz/9d5594e1ac2e73eeee17d761c2b3fd83 to your computer and use it in GitHub Desktop.
Leaderboard Scoring Feed
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| [ | |
| { | |
| "ID": 0, | |
| "Tour": "PGA Tour", | |
| "TourLogo": "http://logo", | |
| "Date": { | |
| "Start": "2012-04-23T18:25:43.511-0500", | |
| "End": "2012-04-23T18:25:43.511-0500" | |
| }, | |
| "Status": "Pending | Ready | Live | Intermission | | Suspended | Finished | Closed", | |
| "EventType": "StrokePlay", | |
| "StrokePlayLeaderBoard": { | |
| "State": "Ready | Live | Intermission | Finished", | |
| "Data": [ | |
| { | |
| "ID": 3, | |
| "Name": "Golfer Name", | |
| "FlagUrl": "http://flag", | |
| "Position": "T2", | |
| "Ordinal": 3, | |
| "Total": 10, | |
| "Today": 10, | |
| "NextTeeTime": "2012-04-23T18:25:43.511-0500" | |
| } | |
| ] | |
| } | |
| } | |
| ] |
Good point. However, is it possible to use this schema in a GET endpoint for bootstrapping purposes? POST updates can be player level only.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think the event level information really needs to be separated out from the data to allow us only to send player level updates over the wire. With this schema, we are stuck sending all 150 players each time