Book Image

RestKit for iOS

By : Taras Kalapun
Book Image

RestKit for iOS

By: Taras Kalapun

Overview of this book

<p>RestKit is an iOS framework for streamlining communication with web services, and it relies on the AFNetworking library that is used by thousands of app developers. It has an interface that is elegant and well designed, and it provides a powerful object-mapping engine that integrates well with the CoreData database. RestKit for iOS will teach you everything from loading a simple list of objects to creating a fully-featured app.<br /><br />RestKit for iOS delivers constructive tools and insights into app development that will benefit any app developer. The book starts with a simple example and then moves on to more complex ones as your knowledge increases. By the end of the guide, you will be able to build a fully-featured app that uses RESTful web services and performs CRUD object manipulation.<br /><br />RestKit for iOS will provide you with all the information you need to boost the development process of both simple and complex apps. Once you have executed a simple example and reviewed the basic theory, you will move on to more advanced concepts with descriptions of real-life scenarios and how to overcome bottlenecks. RestKit for iOS is full of real-life examples that show you how to simplify data loading, basic and advanced object mapping, metadata mapping, and routing. This book also teaches you about routing, RESTful object manipulation and synchronization, integration with the user interface, and caching</p>
Table of Contents (13 chapters)

Requesting related objects


Every MongoDB database has a collection, which consists of documents. While we didn't get to the creating objects topic in our guide, to create a collection manually go to MongoHQ's web console, select a database, and click on the Add Collection button.

You can then name your new collection and click on the Create collection button as shown in the following screenshot:

Creating a new Collection in a web interface

Checking the collection API documentation, we will see a request path /databases/:db/collections. The :db in this path is a parameter, and should be equal to a database name. I prefer calling it databaseID. Such a name reflects the true essence of a parameter as the database name is a database identifier here.

So to load our collections, we will use a path pattern, /databases/:databaseID/collections. The mapping setup for collections looks quite similar to the database mapping:

- (void)setupCollectionMappings
{
    RKObjectManager *manager = [RKObjectManager...