necessary to migrate to Web API from MVC controller
Since the released of Web API, I’ve been wondering whether it’s necessary or helpful to migrate/change MVC controllers to use Web API calls. Since it’s hard to describe code I’ll show an example of what I mean:
necessary to migrate to Web API from MVC controller
Since the released of Web API, I’ve been wondering whether it’s necessary or helpful to migrate/change MVC controllers to use Web API calls. Since it’s hard to describe code I’ll show an example of what I mean:
Modelling REST endpoints with data that not all users have access to
I am trying to figure out the best way around a small problem i have with a design for a Hypermedia API i am currently building.
Is it safe to transmit access tokens via HTTP headers?
It’s the first RESTful web service and I am concerned about security issues. Is it safe to transmit my access token via HTTP headers? For example:
Rest API and caching data
I have developed an application where you should be able to browse products catalog(READ ONLY) even network access is down no wifi or 3g/lte etc. Clients(windows,ios,android etc) consume the rest api. So far There is a REST api that grabs parts like categories with products and other api call to get preferences etc. This adds logic at client like joining them together something that developers dont like.
Rest API and caching data
I have developed an application where you should be able to browse products catalog(READ ONLY) even network access is down no wifi or 3g/lte etc. Clients(windows,ios,android etc) consume the rest api. So far There is a REST api that grabs parts like categories with products and other api call to get preferences etc. This adds logic at client like joining them together something that developers dont like.
Rest API and caching data
I have developed an application where you should be able to browse products catalog(READ ONLY) even network access is down no wifi or 3g/lte etc. Clients(windows,ios,android etc) consume the rest api. So far There is a REST api that grabs parts like categories with products and other api call to get preferences etc. This adds logic at client like joining them together something that developers dont like.
Should a RESTful API provide data for an entire form?
Let’s say I have a JavaScript web application which entirely uses a RESTful API for data.
Should a RESTful API provide data for an entire form?
Let’s say I have a JavaScript web application which entirely uses a RESTful API for data.
Should a RESTful API provide data for an entire form?
Let’s say I have a JavaScript web application which entirely uses a RESTful API for data.