Part 3/3 - It's all about the mapping

All Parts: 1 - 2 - 3 Last week I defined the interface of the Client and its Authenticator. Together with the definition of the endpoints (first part) it is now possible to take a deeper look into the actual network request. But before doing that I need to clarify one important part: the mapping of the response. Mapping JSON (or other transport formats) is a different topic, especially in Swift. »

Part 2/3 - Defining a readable and safe interface

All Parts: 1 - 2 - 3 In the first part I built the foundation for a protocol oriented network abstraction written in Swift. The main focus for the component lies on safety, code quality and a very clean API. Safety is mostly about the rules you define on how the component can be used. In the best scenario the user can not even compile the program if the component is configured wrongly. »

Part 1/3 - Writing a protocol oriented network abstraction in Swift

All Parts: 1 - 2 - 3 Todays topic is very technically. So if you are not interested in programming (or especially in Swift programming), this post might not be for you. This is the first blog post of a short series. Before starting with the structure and the implementation details, I would like to explain how that┬átopic came up. In summer 2014, right after the announcement of Swift, I created a YouTube Channel. »