Geolocation is one of the most powerful features of Backendless. The geolocation service provides APIs for storing, searching and managing geolocation data. There are three main elements that the geolocation service operates on: geocategories, geopoints, and points metadata.
In a previous post, we described how to use the custom business logic code generator to create Backendless timer code. The previous post left off at the step when the Backendless Console created the code.
In a previous post, we wrote about Backendless server-side timers – blocks of code which run on a pre-defined schedule. A timer is a Java class and can be created by hand. The most tedious part is figuring out the scheduling definition. Currently, this is done by declaring the timer’s schedule through a JSON object…
Backendless database provides a very simple, but powerful API for storing, searching, updating or deleting application objects. The “feature 1” post demonstrates how to save objects with relations in Backendless using the APIs.
Another article we wrote gave an introduction to Backendless pub/sub messaging which included a sample for broadcasting and receiving messages. Today we are going to show how to use Backendless messaging for conditional message delivery.
In another post, we described how to adjust an object’s access control list (ACL) using Backendless Console. As we mentioned, in addition to Backendless Console, the object’s permissions can be controlled using API.
As data objects are being saved or updated with the API requests some properties of the objects may not have a value assigned to them. It may be necessary that for those properties a default value is assigned. This is identical to how relational databases may have a default value for a column.
As soon as you have data in persistent storage, the question of searching would be one of the first to come up. Indeed, how can you query the backend for data? We considered multiple options and elected to use the most popular one – SQL.
Once a user of a Backendless-powered app logs in, a session is established. For a variety of reasons, including application security, it is best not to allow users to remain logged in indefinitely. Therefore, every session has an inactivity timeout timer that is reset with every new API call made within the session. When the…