“Software is Eating the World” is a quote attributed to Marc Andreessen and somewhat further explored by his business partner Ben Horowitz. Mark Andreessen gives compelling reasons to validate this quote. To some extend I have to agree with some of his reasons (but I am also a little bit biased as a software engineer). On the other hand, when I read this (and this is partly based on working in different domains on software), I wonder if software is that disruptive? If you look “under the hood” of software applications, you find that a lot of software is based on fundamental software principles that are already 20-30 years old, yet Read More »
“Software is Eating the World” is a quote attributed to Marc Andreessen and somewhat further explored by his business partner Ben Horowitz. Mark Andreessen gives compelling reasons to validate this quote. To some extend I have to agree with some of his reasons (but I am also a little bit biased as a software engineer). On the other hand, when I read this (and this is partly based on working in different domains on software), I wonder if software is that disruptive. If you look “under the hood” of software applications, you find that a lot of software is based on fundamental software principles that are already 20-30 years old, yet they are still frequently used (and for good reasons). That does not mean there are no new advances in software, however old and proven technologies still play an important role (like we say in mathematics, it does not become old, it becomes classic).
So maybe the reason that “Software is Eating the World” is due to the advances in hardware? Would you run modern enterprise applications in the Cloud 20 years ago? One of the challenges could certainly be the bandwidth. Was the IPhone a victory for software or hardware? A lot of the IPhone GUI was not that revolutionary IMO but the combination of hardware and software made for a potent technology disruption.
Last week, my colleague Rajiv walked you through an overview of how our Mobility Services API now supports REST based APIs. As a developer for the Mobility Services Engine (MSE) team, I am very excited about this update because it means that it will be easier for developers to create apps using the MS-API, which hopefully means that more and more organizations will be able to take advantage of the location-based services and functionalities of the MSE. I’m going use this blog to walk you through some of the more technical aspects of the change.
The REST API is now widely used in the field of API based web applications. The REST stands for REpresentational State Transfer. It is an architecture that is based on set of six rules, and APIs that support REST follow all those rules, making them RESTful.
Compared to SOAP, REST has better performance, scalability, simplicity, modifiability, visibility, portability, and reliability. For secured REST API transactions, HTTPS is recommended.
RESTful Mobility Services API
7.5 applications, including features from the Connected Mobile Experiences (CMX) solution such as Browser Engage and CMX Analytics, are now supporting REST APIs in addition to the existing SOAP APIs previous releases (backward compatibility).
CMX utilizes the basic authentication scheme to authenticate each REST API request. It utilizes the Authorization header in the HTTP packet. The Authorization header is composed as follows:
– Username and password are combined into a string “username:password”.
– The resulting string literal is then encoded using Base64.
– The authorization method, a space and the string “Basic” is then put before the encoded string.
The API credentials can be accessed from Prime Infrastructure (PI), which manages CMX (page is located under Mobility Services > Specific MSE > System > Users).
As Rajiv mentioned last week, the Mobility Services REST APIs can be grouped in the following way:
– MAP APIs
– Real time location APIs
– Location history APIs
– Notification APIs
Let’s break them down with use cases to get a better picture of when you’d use which. Read More »
Tags: API, App, app developer, application, application developer, application development, code, Development, engineer, location, location based services, map, mobility, mobility services, mobility services engine, MS API, mse, network, REST, SOAP/XML, technical, technology, wifi, wireless
As a product manager, I am happy and excited to tell you that Cisco Mobility Services Engine (MSE) now supports REST based APIs. Why am I happy and excited you ask? MSE’s REST based APIs allow web app developers to rapidly develop location aware apps with ease. Let me walk you through this new feature at a high level, and my colleague will take you through a closer look feature blog next week.
Mobility Services Engine and API support
For readers who are not familiar with the Cisco Mobility Service Engine and the APIs, here’s the gist:
– Cisco Mobility Services Engine (MSE) works in conjunction with Cisco Wireless LAN Controller (WLC) and Cisco Aironet Access Points (APs) and computes real time location for all Wi-Fi end-points using RSSI based triangulation algorithms.
– MSE stores real time and historical location of Wi-Fi clients in its database making it a gold mine of data for indoor location. (Remember that GPS technology is not effective for indoor location)
– This rich store of indoor location data is now available to app developers to query through a REST based API over a secure HTTPS connection.
What can I do with MSE REST APIs?
MSE REST APIs allow web developers to query MSE location database using the HTTP(S) GET method. HTTP response payload can be received in XML or JSON format. Here is a list of resources that are accessible over the REST API. Read More »
Tags: API, Cisco, cmx, connected mobile experiences, HTTP(S) GET, location, location based services, map, mobility services, mobility services engine, mse, real time location, REST, rtls, web developer, XML
Since the launch of Connected Mobile Experiences (CMX), we have seen tremendous interest from our customers to monetize their investment in Wi-Fi Solutions and enable new line-of-business applications to gain insights, deliver efficiencies and engage end-users. This week Cisco is announcing a collection of technology developer partnerships, as managed through the Cisco Developer Network (CDN), that help us bring a “whole offering” to our Customers with the addition of domain expertise, geographical focus and technology feature infusion that gives our Customers confidence, security and operational excellence to move forward in this nascent market.
The foundation of this technical integration begins with the connection to the Cisco WLAN & Unified Access Architecture through the Mobility Services API, which exposes context-aware information gathered by the Cisco Mobility Services Engine (MSE) for the integration with following disciplines: Read More »