The latest version of the Azure Mobile Services SDK for Android added support for both futures (for asynchronous operations) and offline (disconnected applications). In this post I’ll walk through the offline feature, by walking through the steps required to make the sample application downloaded from the portal (To do list) offline-enabled. We’ll be talking about the features as they’re needed for the app.
Posts By: Carlos Figueira
Addressing feedback on the usage of asynchronous calls in Android, we’ve released a major update in the Android SDK for Azure Mobile Services with futures support. With that, you can now easily perform multiple of those operations without having to deal with multiple nested callbacks. The changes are additive in most of the scenarios, but in some advanced scenarios we made a breaking change to make futures the default model used by the Azure Mobile Services Android SDK for dealing with asynchronous operations.
In my previous post I showed how to use tables in an Azure Mobile Services node.js backend to talk to a MongoDB collection for simple CRUD operations. In this post we present a way retrieve all OData query parameters passed to the table read script, so that we can support more complex read operations into the Mongo database.
Unlike in the .NET backend, the node.js backend of Azure Mobile Services doesn’t have native support for MongoDB collections. We can, however, implement it in a node.js mobile service by using table scripts. This post shows how to add basic support for CRUD operations from a Mongo database to your mobile service.