public marks

PUBLIC MARKS from Spone with tag rest

2016

Why You Should Taste Grape – Glauco Custódio – Software engineering, open source, community and passion

I know that Rails 5 with --api mode is around the corner. But I need to say you how awesome is to build APIs with Grape. I will show you why. What are the main features we expect from a good API? Parameter validation Parameter coercion Documentation Serialization Performance Versioning Authentication Testing The first four items are the ones in which Grape really shines for me. I am going through one at a time.

2014

2013

Best Practices for Designing a Pragmatic RESTful API | Vinay Sahni

Your data model has started to stabilize and you're in a position to create a public API for your web app. You realize it's hard to make significant changes to your API once it's released and want to get as much right as possible up front. Now, the internet has no shortage on opinions on API design. But, since there's no one widely adopted standard that works in all cases, you're left with a bunch of choices: What formats should you accept? How should you authenticate? Should your API be versioned?

2011

georest - Project Hosting on Google Code

GeoREST is a web-centric framework for distributing geospatial data. It allows RESTful feature-based access to spatial data sources, including full editing capabilities, through a MapGuide server or directly via FDO.

FRAPI | Focus on business logic, not presentation

by 1 other (via)
FRAPI is a high-level API framework that puts the “rest” back into RESTful. Use it to power your web apps, mobile services, and legacy systems.

Spone's TAGS related to tag rest

api +   best practices +   design pattern +   données +   données publiques +   framework +   geospatial +   javascript +   mobile +   php +   rails +   ruby +   security +