Book Image

Hands-On Server-Side Web Development with Swift

By : Angus Yeung
Book Image

Hands-On Server-Side Web Development with Swift

By: Angus Yeung

Overview of this book

This book is about building professional web applications and web services using Swift 4.0 and leveraging two popular Swift web frameworks: Vapor 3.0 and Kitura 2.5. In the first part of this book, we’ll focus on the creation of basic web applications from Vapor and Kitura boilerplate projects. As the web apps start out simple, more useful techniques, such as unit test development, debugging, logging, and the build and release process, will be introduced to readers. In the second part, we’ll learn different aspects of web application development with server-side Swift, including setting up routes and controllers to process custom client requests, working with template engines such as Leaf and Stencil to create dynamic web content, beautifying the content with Bootstrap, managing user access with authentication framework, and leveraging the Object Relational Mapping (ORM) abstraction layer (Vapor’s Fluent and Kitura’s Kuery) to perform database operations. Finally, in the third part, we’ll develop web services in Swift and build our API Gateway, microservices and database backend in a three-tier architecture design. Readers will learn how to design RESTful APIs, work with asynchronous processes, and leverage container technology such as Docker in deploying microservices to cloud hosting services such as Vapor Cloud and IBM Cloud.
Table of Contents (18 chapters)

Using the Delegate Pattern

In iOS programming, it is common to use the delegate pattern for one component to pass information to another. The delegator component defines a delegate protocol with functions that it can use to pass out information. The delegatee component implements the provided delegate protocol by overriding the protocol's functions and handles the received information.

In your case, the new screen for adding a new entry is the delegator, while the main screen with table view is the delegatee to whom the information is passed.

Create the following delegate protocol in the same Swift file as the EntryDetailsViewController class (delegator) so it can inform MainScreenViewController (delegatee) when user is done creating the new entry:

protocol EntryDetailsViewControllerDelegate: class {
// Delegate Cancel Event
func entryDetailsViewControllerDidCancel...