Google Maps – Geofence a route
I’m looking at implementing a PHP based application, where by you have a certain route for example London to Edinburgh. Along this route, I want to calculate say a 10mi Radius or Polygon around the whole route/driving directions, check whether certain defined points/lat-lon’s are within this radius. If so – Add them to the waypoint list, re-calculate the route and re-generate the driving directions.
Does decoupling trump DRY in REST?
I am building a REST API to expose most of functionality of an existing Java API. Both APIs are for internal use within my organization; I do not have to design for external use. I have influence over both APIs but am implementing the REST one. The Java API will continue to be used for local applications (it’s not being “retired”), but the REST API will be used for significant new development.
Implementing the command pattern in a RESTful API
I’m in the process of designing an HTTP API, hopefully making it as RESTful as possible.
Library design: provide a common header file or multiple headers
There are essentially two camps of library designers concerning the design of the final header file inclusion:
Management wants an API in purchased software
My company wants to purchase new software for our General Ledger. We want to be able to interface it with various other sytems, all purchased. Nothing is custom built. The software our Accountants like does not have any APIs. However it does allow for imports and exports through various file formats.
Encapsulate external JavaScript library
I am about to develop a ASP.NET MVC 4 project that will make use of maps. Our company has it’s own map API which is very basic at the moment, but is intended to be further developed in future to match some specific customer needs.
The project will have a mobile/tablet interface in addition to it’s web interface and needs to be developed now. So we have planned to start use the Google Maps v3 API.
When to use nested resources in a RESTful API
I have two resources: users and links.
Workflow for building a RESTful API
I am building a RESTful API, and so far, to make sure that my resources work as I need them to, I am using a REST client called Postman. This makes it easy for me to store routes and quickly make requests to them for testing. My current collection of routes in Postman looks like this:
Is it possible to use a “non-commercial” REST API in a for-pay app?
I am interested in integrating the results of 3rd-party news API’s into my for-pay application. The APIs would be a very small part of the app (e. g. the app is not just reselling the APIs). I have found that many APIs such as Yahoo have “non-commercial” conditions like the following:
Is it possible to use a “non-commercial” REST API in a for-pay app?
I am interested in integrating the results of 3rd-party news API’s into my for-pay application. The APIs would be a very small part of the app (e. g. the app is not just reselling the APIs). I have found that many APIs such as Yahoo have “non-commercial” conditions like the following: