This is a notification about an upcoming change in the behavior of CodeRunner – a Backendless container responsible for executing custom business logic. An upcoming release will introduce a change that will change the behavior of CodeRunner with regards to the Backendless API calls made by custom code. Currently, custom business logic can make both…
IDC published a Watchlist Report on Backendless.
We are preparing a new maintenance release with important bug fixes and improvements. One of the changes in the release breaks backwards compatibility for REST clients. The scope of the change is rather minor: any data object property marked as DATETIME will be serialized (from server to client) as a number (a timestamp) representing the…
Backendless partnered with Acrodea to enter the Japanese and Korean mobile application development markets.
I am very excited to report that we have an amazing new release with some very cool functionality ready for you. Among the new features you will find support for video streaming and broadcasting for Android, support for Atomic Counters and Caching API. Additionally, we have revised our pricing to give you more choices and more…
In addition to the built-in events triggered by the API calls, Backendless supports custom, developer-defined events. Custom business logic code, which is executed on the server-side, can be attached to either built-in events or the developer-defined ones. Custom events can be triggered through a specialized API call from a client library or by other custom…
There are a lot of scenarios when custom business logic on the server-side may need to connect to an external host. Whether it is a service call to a third-party service or a retrieving data from a proprietary system, the code must establish a connection to an external host. Up until now if you tried…
We build and release a lot of software – core service, 5 SDKs and a special utility for custom business logic. We always wanted to visualize our release history to make it easy to navigate through the releases and see how a specific SDK or the core service is evolving. Today we release our release…
Back for round #2, eh? (if you missed the first post which was about registering users, read it here) Well, let’s dive in. This one should be pretty quick. The following code is pretty well commented, ping me if you have any questions. json = require (“json”) — Create a table to hold our headers…