You are reading a single comment by @Velocio and its replies.
Click here to read the full conversation.
London Fixed Gear and Single-Speed is a community of predominantly fixed gear and single-speed cyclists in and around London, UK.
This site is supported almost exclusively by donations. Please consider donating a small amount regularly.
@Velocio
The API is JSON only this second, though I want to also offer XML and others eventually. No WSDL today... do you really want one? Really? I don't know anything that can generate them from Go interfaces, I'd have to write it by hand which is a PITA.
Auth mechanism is likely OAuth 2.0, using this lib should you be interested: https://code.google.com/p/goauth2/source/browse/oauth/oauth.go
Though auth suggests applications and permissions, and permissions makes me think about users and all of that about security, logging, rate-limiting, usage data... and whilst I know what approach I'm taking I want to get core data structure concepts right before addressing the cross-cutting concerns.
And yes, GET requests will vary by headers, be cached by Varnish, and may result in a 304 on cache hit and browser already having a copy.
It's way too early for an Android app... can I delay you until January?
What I'm looking for now is: This makes sense, I can navigate around the API and understand what exists and roughly how I'd call it.
Then: Are there any obviously massive things you might expect to be possible content-wise that you're not seeing? Are there any refinements to the resources that you'd propose?