This tutorial explains how to create and consume a WCF service in ASP.NET.
Tag Archives: Web Services
With the web services that are popping from your corporate networks to the wild-internet, accessing HTTP based resources is becoming a critical component to any and all application development. One of the more popular API application design styles is Representational State Transfer (or REST). REST implementations are typically developed on top of HTTP with the objects you are effecting being in the URI and the actions, or verbs, being the HTTP methods. The HTTP methods follow the four basic methods of persistent storage as referenced in the CRUD acronym of Create, Read, Update, and Delete acronym.
Rashmi Jayakumar is .Net Lead has 8 years of IT Industry experience and 8 years of relevant experience. Her current location is Bangalore, India and She is willing to relocate anywhere in USA. Her area of expertise are WCF, Web API’s, Web services, APIGEE, REST/SOAP API’s. She has Valid H1B visa till 2017. She is available with in 4 week. If interested please E-mail her at firstname.lastname@example.org
As described in the first part of this two-part series, “Create a Web Service with Azure Web Apps and WebJobs” (msdn.microsoft.com/magazine/mt185572), in the August issue, many mobile apps today are connected to one or more Web services that provide valuable and interesting data. Although it’s easy to just make direct REST API calls to those services and process responses in the client, such an approach can be costly in terms of battery power, bandwidth and throttling limitations imposed by different services. Performance might also suffer on lower-end hardware. It makes sense, then, to offload work to a custom back end, as we demonstrate with the “Altostratus” project we’ll discuss in this article.
Templating is a huge part of web services. It allows developers to express values from inside their markup (HTML) and have them show up in the output. Templates are valuable because, servers can respond with data based upon the request itself, instead of just using static HTML files.
As Software Developers , we sometimes need to create a simple server that can accept some REST queries without wasting too much time. It’s always appealing to build our own components as it ensures our needs will be met. While REST sounds basic and easy to implement, to get a full REST server working is not trivial, especially when you want shiny features like HATEOAS ( https://en.wikipedia.org/wiki/HATEOAS ), pagination support, query filter, multiple content type (JSON, XML, plain text, …) support, If-Match/ETag, etc.
Let me walk you through a simple way of doing this using Python-Eve and Eve-SQLAlchemy.
CloudKit helps developers manage static data and almost every App needs some static data to function properly. By static data, I mean, non mutable data. Apps that use non mutable data could be:
- an App that stores information about a URL and an API key locally so that it can connect to some web service;
- a reference App, such as a dictionary or a translator, that needs to quickly access the dictionary entries in order to work offline;
- a quiz game, like a trivia App, that needs access to the questions and answers so that users can play offline.
Most of the time, these data need to be available at the application launch. So, we usually store this information in the App. However, we have an issue here: if we need to change these data for any reason, we will need to upload a new App version to the App Store. And you know, because we must wait a few days to pass the review , this process is not instantaneous. And it won’t be until our users get the update that everything will run smoothly again.
So, it seems that this is not the best process. In general, you don’t need to change the static data every time you send a new app version to the App Store. But there are some uncommon situations that require a solution as quickly as possible. For example, imagine that the API key of your app became invalid. Maybe someone hacked your account, stole the API keys and started to use them incorrectly, costing you thousands of dollars, and putting the privacy of your users at risk. In this case, we would need to reset the API key as soon as possible, but going through the review process can be killer.
Though this never should happen, it can happen. And while you’re trying to find out who hacked your account, time is passing. Your App is losing the momentum, or, worst case, not working at all. So, we have to fix it, and we have to do it now!