jlouvel
Re:How to do API Versioning?
on Tuesday April 28, 2015 @08:42PM (#9455944)
Restlet team has answered in this GitHub issue:
https://github.com/restlet/restlet-framework-java/issues/105...
Re:How to use a Google Spreadsheet as a database
on Wednesday March 25, 2015 @06:04PM (#9266286)
APISpark (PaaS for APIs) is capable of creating a REST API (JSON/YAML/XML formats) on top of a Google Spreadsheet, using it as a database:
http://restlet.com/technical-resources/apispark/tutorials/tu...
In the latest version, it comes with a server-side API cache to prevent GSheet latency and availability issues.
Note: I'm the founder of APISpark
Re:Ask HN: What's the best way to write an API spec?
on Tuesday January 20, 2015 @09:48AM (#8917134)
Restlet Studio (http://studio.restlet.com/) let's you visually craft your REST API and then view it as Swagger 2.0 or RAML 0.8 source code by simply switching tabs.
It is entirely free and available as a simple web app and installable as a Chrome app. Disclaimer: I work at Restlet.
Re:AWS issues unavoidable reboot schedules with short notice on many E...
on Thursday September 25, 2014 @04:31PM (#8369574)
We had a similar experience regarding DynamoDB.
Re:Show HN: Sheetlabs – Turn your spreadsheets into APIs
on Monday July 07, 2014 @04:51PM (#8001315)
There is also APISpark, a full stack PaaS for web APIs, that provides a "spreadsheet-to-web API" feature.
It works both in read and write mode. See tutorial: https://apispark.com/docs/tutorials/google-spreadsheet
APISpark adds Swagger-as-a-Service functionality
RESTistential Crisis over Hypermedia APIs
Show HN: Restlet Framework 2.2.0 and 2.3 M1. Support for Java 6, Guice and Swagger
Re:Designing a Pragmatic RESTful API
on Wednesday June 05, 2013 @04:33AM (#5824328)
I fully agree. Fielding warns in his dissertation about design by buzzwords himself.
Almost all web APIs out there aren't REST APIs because they don't respect the "driven by hypermedia" constraint which makes sense because this constraint was put in place for human users driving applications through web browsers, not for machines.
I've started to formalize a new "Web API" architecture style that takes the best of REST but leaves the requirements and constraints that don't make sense. See this blog post: http://blog.restlet.com/2013/05/02/how-much-rest-should-your...
Re:How much REST should your Web API get? Hypermedia APIs & cross-devi...
on Friday May 03, 2013 @02:47AM (#5649173)
Thanks, I'll continue the formalization of this style over here: https://github.com/restlet/web-api-style