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 asynchronous and synchronous calls. With the new update, the asynchronous API calls will be disabled in CodeRunner. If you have any custom business logic currently deployed or planning on deploying it soon, it is very important to make sure that the code does not use any asynchronous calls. Changing the implementation should be very easy – simply remove the AsyncCallback argument from the API calls and refactor the code for the synchronous mode (moving code from the async callback handlers). The change will be made live Wednesday, October 29th at 8am CDT.
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 number of milliseconds since January 1, 1970, 00:00:00 GMT. Currently these values are returned as String objects in the following format: “MM/DD/YYY hh:mm:ss timezone”. This change will go on effect on September 24th at 8am US Central time. If you have any questions, please contact us via the support forum.
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 value for the money. Continue reading
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 business logic. Dispatching a custom event may have event arguments. The server-side code which handles an event may also return a value to be delivered back to the client-side that dispatched the event. This feature can be used to invoke custom business logic from the client-side. Developing custom event handlers is very easy with Backendless – you can register an event using Backendless console, which automatically generates the source code required for declaring an event handler. Just like with the built-in events, custom event handlers can be debugged on the developer machine before the code is pushed to production. Continue reading
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 to connect elsewhere except for Backendless’ API endpoint, you’d be getting an exception in your custom server-side code – we used to block all hosts. Today we released an update which allows you to connect to any computer located elsewhere. The process of establishing a connection does not change – you can connect to any port using any protocol. However, the hosts to which your connect connects, must be registered with Backendless. We have added a special section in Backendless console, which you can see at Manage > App Settings > External Hosts: