Spatial support in Web API and ODATA

יום שלישי, יוני 3, 2014

The spatial support in ASP.NET WEB API is currently very limited. When creating a WEB API project a reference to System.Spatial is created automatically. When creating an OData 4.0 (WEB API 2.2) a reference to Microsoft.Spatial is created. Both System.Spatial and Microsoft.Spatial are actually the same. It is the spatial library that was developed for WCF Data Services and can be installed by importing the NuGet package Microsoft.Spatial. Microsoft.Spatial contains wide collection of spatial types and formatters for GeoJson and GML. Unfortunately this is where the WEB API and ODATA support for spatial functionality ends. The OData standard defines...
no comments

WAAD, OAuth and Javascript

יום שלישי, מרץ 4, 2014

As you probably know Microsoft released AAL (Windows Azure AD Authentication Library for .NET) which is a great API for interacting with WAAD and implement the OAuth code flow. This API is extremely easy to use yet it works only for single threaded (STA) clients. It means that you can use it in a console application or windows store app but not in a browser. The scenario in which a client wants to call a web api in a SPA (Single Page Application) looks very interesting so I searched for an JavaScript SDK for WAAD but I could not...
no comments

Seven-Steps for Designing a web API

יום חמישי, ינואר 2, 2014

This is the procedure described by Leonard Richardson in his book : RESTful Web APIs . The procedure consist of seven steps. Doing some preparatory workup front will help you choose a representation format and keep your profile as simpleas possible. 1. List all the pieces of information a client might want to get out of your API or putinto your API. These will become your semantic descriptors.Semantic descriptors tend to form hierarchies. A descriptor that refers to a realworldobject like a person will usually contain a number of more detailed, moreabstract descriptors like givenName. Group your descriptors...
no comments

Basic rules for building REST web APIs

We have a client-server Internet protocol, HTTP, which assigns very general meanings to different kinds of requests: GET, POST, PUT,and so on.We have the idea of hypermedia, which allows the server to tell the client which HTTP requests it might want to make next. This frees the client from having to know the shape of the API ahead of time.We have the idea of application semantics, which extend hypermedia controls with information about what specifically will happen, to application or resource state, if the client makes a certain HTTP request.And finally we have a whole lot of standards for...
no comments