18.json (2016B)
1 { 2 "number": 18, 3 "title": "Use lastUpdate variable", 4 "state": "open", 5 "author": "MTRNord", 6 "created_at": "2017-02-16T09:54:00Z", 7 "closed_at": null, 8 "labels": [ 9 "enhancement" 10 ], 11 "assignees": [ 12 "MTRNord" 13 ], 14 "body": "Use lastUpdate Variable to do auto refresh", 15 "comments": [ 16 { 17 "author": "johan12345", 18 "created_at": "2017-02-16T09:56:18Z", 19 "body": "`lastUpdate` only shows the last time where the server refreshed the schedule from the school website (which is approximately once per minute). I'm not sure if that is what you need." 20 }, 21 { 22 "author": "MTRNord", 23 "created_at": "2017-02-16T10:18:30Z", 24 "body": "Ah I thaught that it shows when there was the last time something different :/" 25 }, 26 { 27 "author": "johan12345", 28 "created_at": "2017-02-16T10:20:36Z", 29 "body": "No. There is the `lastChange` field that shows the \"Stand\" from the schedule (but that's not necessarily the same time when it was uploaded to the website and downloaded by my server)." 30 }, 31 { 32 "author": "MTRNord", 33 "created_at": "2017-02-16T10:22:40Z", 34 "body": "Ok than that is the better way to go. Means I can check if that (`lastChange` ) changed from the previous request?" 35 }, 36 { 37 "author": "johan12345", 38 "created_at": "2017-02-16T10:24:34Z", 39 "body": "You can, but I can't guarantee that there is no change on the schedule when `lastChange` did not change (because the school might be able to edit the schedule without updating the displayed \"Stand\"). Why don't you just compare the whole schedule?" 40 }, 41 { 42 "author": "MTRNord", 43 "created_at": "2017-02-16T10:25:26Z", 44 "body": "Wanted to keep it fast :) It is a little faster to compare 1 field vs multiple fields. But I will try both" 45 }, 46 { 47 "author": "johan12345", 48 "created_at": "2017-02-16T10:26:03Z", 49 "body": "Well, with today's computing power you probably won't notice \ud83d\ude09 " 50 } 51 ] 52 }