Message:

Subscribe rss
Blog categories

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:

external hosts - Connecting to external hosts from custom business logic

Continue reading

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 history. You can see it at:
https://backendless.com/backend-as-a-service/release-history/

The system let’s you see our progress and the history of changes for everything we develop. Go ahead and play with it and let us know what you think.

release history 300x280 - Interactive Release History

Enjoy!

Posted in Status

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.

This should bring back something similar to:

Notice the Backendless specific things, we didn’t create those fields in our previous post when we added this user to the database.

  • objectId
  • userStatus

Don’t panic, Backendless adds these automatically. Here’s our expected fields we created in the first post:

  • username
  • email
  • password…..wait, what the?!?! Where’s the password?!

I was expecting to be able to see the password when we query the user info, however, for security Backendless encrypts the password info in a one-way method that even they (or you as the admin of your user table) can’t retrieve. If a user forgets their password, you’ll have to build in the functionality for them to reset it.

I don’t have all the answers, so I hit up their great community and got a response. Check my post here for a more in depth explanation of their encryption.

How do you get the data to compare what the user is entering VS what’s stored on the backend? That’s where the login functionality comes in to play. We’ll hit that up in the next post.

My mission is to keep these posts nice and bite-sized. I don’t want to overwhelm you with tons of functionality. I’m mirroring Backendless’s docs for the REST API.

See you soon!

Mario

This post will go over the basics of integrating Backendless services into the Corona framework…

First, create your Backendless account and obtain the “application-id” and “secret key”. Keep those handy, you’ll be using them throughout these tutorials.

At present, there is not a proper, Corona-specific API plugin so we’ll be using the REST API for Backendless. A handy link can be found here for the REST documentation.

Continue reading

Scheduled tasks or background jobs is a common requirement for a lot of applications. Backendless supports this concept through a feature we call Timers. A timer is a form of custom server-side code which runs on a pre-defined schedule. This video demonstrates the process of developing a timer, testing it in the debug mode and publishing into the production environment. This is our second video reviewing custom server code. The first video is available in the “Developing Custom Server Code with Backendless mBaaS” blog post.

As an mBaaS platform we frequently say “no server-side coding is required”. This is true for a lot of apps, however, at times it is necessary to shift some application logic to the server-side. The logic may need to alter or extend the default implementation of the core services. Adding custom business logic is not only easy with Backendless, but the process is really cool and exciting. The combination of a code generator with the local debugging option makes it a killer feature. The video below will walk you through the process of adding custom business logic to Backendless. Enjoy!

Geolocation is one of the core services of Backendless.

Using the Geolocation API you can easily add a sense of location to your application. Backendless provides a powerful mechanism for metadata-based searches in a geographic area (rectangle or radius). The latest release of Backendless includes an entirely rewritten Geolocation management interface in the Backendless Console.

This video provides an overview of the capabilities we added to the product:

We just pushed a new release to our production servers. The release includes multiple new features and a ton of improvements. Below is a summary of what went into the release. There will be a blog post with a video providing an in-depth review of each new feature:

Continue reading

cocoapods stickers 300x160 - Using Backendless CocoaPod with XCodeCocoaPods manages library dependencies for your Xcode projects.

The dependencies for your projects are specified in a single text file called “Podfile”. CocoaPods resolves dependencies between libraries, fetches necessary code and links it together in an Xcode workspace to build your project.

Continue reading
Posted in iOS

This article reviews the APIs for working with relational persistent data in Backendless. By the end of the article, you will have a working application which demonstrates various mechanisms for loading related data objects from the backend-as-a-service data store. To avoid any terminology confusion or overlap, let’s define related data as multiple objects referencing one another in the object-oriented data model. For example, suppose there is a class called Order. The class aggregates (references) a collection of OrderItem’s. This is a one-to-many relation. The OrderItem class has a one-to-one relation with a class called Manufacturer. Consider the following diagram: class model - How to Load Relational Data from mBaaS

Continue reading