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
With keg.io live on the web, our json request url's are wide open to anyone who might want to do something with our data. We can add a few more API call options, and add in a callback wrapper for crossdomain ajax use. Then tell people to have at it.
-Pour History
-Last Drinker (new API method)
-Current Temperature (new API method)
-Current Keg
The text was updated successfully, but these errors were encountered:
I'm not sure how many people I want querying the data right this second. Seems like we should get it a bit more stable (no server crashes) before telling people to start making api calls. Also I'm not sure how good of a long term machine the thin client is running on a CF card.
We could pseudo-restrict access by throwing some random, but required, query string parameter on the HTTP request. We can then only share that with people as they request access... kind of like request a beta invite type launches.
With keg.io live on the web, our json request url's are wide open to anyone who might want to do something with our data. We can add a few more API call options, and add in a callback wrapper for crossdomain ajax use. Then tell people to have at it.
-Pour History
-Last Drinker (new API method)
-Current Temperature (new API method)
-Current Keg
The text was updated successfully, but these errors were encountered: