Message:

API Change (4 posts)

With the introduction of version 4.0 in the Backendless Cloud environment, we set the goal to allow both the current version of 3.x and the new 4.0 to collocate on the same subdomain. When we introduce 4.0 in the Cloud, both versions of the backend will be available on the https://develop.backendless.com domain. As a result, there is going to be a change for the Admin and Management API. The change will require the /3.x  prefix to be added to all API routes except for “Developer Login”. For example, the following route:

would need to be modified as shown below:

This change will go in effect when the 4.0 version becomes available in the Cloud. There will be an additional blog post 24 hours before the release is switched on.

 

Posted in API Change

It feels really amazing to begin writing this blog post. We got caught in an unusually long release cycle, spent months iterating over the new features, improvements and bug fixes, but in the end it was well worth it. We did it! Backendless 2.0 is here and the product is as cool and powerful as ever. With this release we made several very firm steps towards establishing the Backendless Platform – a unified system for designing, developing, running and managing backend services.

The release brings four major new features and about a dozen at а smaller scale. All of the new features are distinct differentiators of our product making it the strongest mobile backend as a service offering on the market. So without any further ado, let me introduce the new additions to our feature line up:

Continue reading

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.

Posted in API Change