URL parameters in RESTful web services
I’m wondering about the appropriateness of URL parameters in RESTful resource creation.
How to achieve a loosely coupled REST API but with a defined and well understood contract?
I am new to REST and am struggling to understand how one would properly design a REST system to both allow for loose coupling but at the same time allow a consumer of a REST API to understand the API.
Wrapping REST based Web Service
I am designing a system that will be running online under Microsoft Windows Azure. One component is a REST based web service which will really be a wrapper (using proxy pattern) which calls the REST web services of a business partner, which has to do with BLOB storage (note: we are not using azure storage). The majority of the functionality will be taking a request, calling our partner web service, receiving the request and then passing that back to the client.
Should I use both WCF and ASP.NET Web API
We already have a WCF API with basichttpbinding.
Some of the calls have complex objects in both the response and request.
API Auth vs User Auth
I have read many posts and articles on this topic but still cant connect the dots. I want to make a Rails app that is strictly a JSON API maybe using Sinatra or the rails-api gem. I also want to make both a web client app and an iPhone app which consumes the API. No plans on letting third party dev’s use it.
How should an API use http basic authentication
When an API requires that a client authenticates to it, i’ve seen two different scenarios used and I am wondering which case I should use for my situation.
How should an API use http basic authentication
When an API requires that a client authenticates to it, i’ve seen two different scenarios used and I am wondering which case I should use for my situation.
Why is nesting or piggybacking errors within errors bad in general?
Why is nesting or piggybacking errors within errors bad in general?
Do server-side sessions violate REST?
According to Roy Fielding (one of the principle authors of the HTTP specification) in his seminal thesis Architectural Styles when discussing REST, he mentions:
How to structure a set of RESTful URLs
Kind of a REST lightweight here… Wondering which url scheme is more appropriate for a stock market data app (BTW, all queries will be GETs as the client doesn’t modify data):