via Implementing a cross platform HTTP Client in the PCL to consume your ASP.Net Web API backend on Azure – Mark’s Blog
When working with a mobile app you will often work with a backend, which if you are working with C# might very probably be a Web API backend. In this blog we will look at how we can consume and write to a Web API Controller that we can host on Azure. Why Azure? Because it is the easiest way of hosting a web service straight out of Visual Studio and if you happen to have a MSDN subscription you can do this all for free. For the client we will be using a Windows 10 Universal App which allows us to write a client for Desktop, Tablet and Phone.
The app we will be building will add the capability to read a list of people from a service and add a person to the existing. So we will see how we can read and write to a HTTP service.
In a previous post I described how to implement HTTP requests using the Google’s library Volley. We saw how to save lot of boilerplate code in such a critical part of our apps like the networking communication with our server using a well tested and reliable library. We showed how straightforward is to have so useful […]
via The API Development Lifecycle – an Introduction.
It’s likely a significant part of your system.
But, a lot of software organizations do not fully utilize the tools and services available to help design, develop, debug, test and monitor their APIs.
In this mini series, we’re going to cover a collection of tools and services to help get the HTTP API into your existing software processes.
Let’s start with developer tools.
There are a number of options for local developer machine scenarios all the way to hosted service solutions that run test suites against your deployed API.
via all and sundry: Polling an http end point using Spring Integration.
It is a little non-intuitive if you want to write a flow with Spring Integration which polls an http end point and gathers some content from the http end point for further processing.
Spring Integration provides a couple of ways for integrating with a HTTP endpoint –
1. Http Outbound adapter – to send the messages to an http endpoint
2. Http Outbound gateway – to send messages to an http endpoint and to collect the response as a message
via jQuery UI Sortable List with Ajax Feedback Example.
The jQuery UI contains a Sortable widget that is ideal for creating sortable unordered list items quickly and painlessly. Using jQuery Ajax, this article will demonstrate one way that the order of list items can be stored and updated on the server without the need for a formsubmit button or page refresh as the user rearranges them. It should be noted that because Ajax occurs each time a user alters the list order this will result in a higher number of HTTP requests to the server than alternative approaches like a traditional form submit or Ajax onsubmit would.
The first thing to do of course is make the list items sortable. This is easily done by applying the jQuery UI sortable method to the unordered list element (the minimum amount of jQuery needed is shown below) providing jQuery and the jQuery UI scripts have been included in the file containing the unordered list. The Sortable UI documentation provides a short example to help with getting started.
As you probably know very well by now, the internet is made up of a bunch of interconnected computers called servers. When you are surfing the web and navigating between web pages, what you are really doing is telling your browser to request information from any of these servers. It kinda looks as follows: your browser sends a request, waits awkwardly for the server to respond to the request, and (once the server responds) processes the request. All of this communication is made possible because of something known as the HTTP protocol.
The HTTP protocol provides a common language that allows your browser and a bunch of other things to communicate with all the servers that make up the internet. The requests your browser makes on your behalf using the HTTP protocol are known as HTTP requests, and these requests go well beyond simply loading a new page as you are navigating. A common (and whole lot more exciting!) set of use cases revolve around updating your existing page with data resulting from a HTTP request.
For example, you may have a page where you’d like to display some information about the currently logged-in user. This is information your page might not have initially, but it will be information your browser will request as part of you interacting with the page. The server will respond with the data and have your page update with that information. All of this probably sounds a bit abstract, so I’m going to go a bit weird for a few moments and describe what a HTTP request and response might look like for this example.
via Swagger for Node.js HTTP API Design | RisingStack.
Swagger is a simple yet powerful representation of your RESTful API. With the largest ecosystem of API tooling on the planet, thousands of developers are supporting Swagger in almost every modern programming language and deployment environment.
With a Swagger-enabled API, you get interactive documentation, client SDK generation and discoverability.