Book Image

PHP Reactive Programming

By : Martin Sikora
Book Image

PHP Reactive Programming

By: Martin Sikora

Overview of this book

Reactive Programming helps us write code that is concise, clear, and readable. Combining the power of reactive programming and PHP, one of the most widely used languages, will enable you to create web applications more pragmatically. PHP Reactive Programming will teach you the benefits of reactive programming via real-world examples with a hands-on approach. You will create multiple projects showing RxPHP in action alone and in combination with other libraries. The book starts with a brief introduction to reactive programming, clearly explaining the importance of building reactive applications. You will use the RxPHP library, built a reddit CLI using it, and also re-implement the Symfony3 Event Dispatcher with RxPHP. You will learn how to test your RxPHP code by writing unit tests. Moving on to more interesting aspects, you will implement a web socket backend by developing a browser game. You will learn to implement quite complex reactive systems while avoiding pitfalls such as circular dependencies by moving the RxJS logic from the frontend to the backend. The book will then focus on writing extendable RxPHP code by developing a code testing tool and also cover Using RxPHP on both the server and client side of the application. With a concluding chapter on reactive programming practices in other languages, this book will serve as a complete guide for you to start writing reactive applications in PHP.
Table of Contents (18 chapters)
PHP Reactive Programming
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

The materialize() and dematerialize() operators


In Chapter 5 , Testing RxPHP Code, when we talked about testing in RxPHP, we weren't using real values, and instead were passing some special recorded objects that wrapped the actual value with OnNextNotification (or its error or complete variants). We did this because of the TestScheduler class and because we had to be able to uniquely identify each value in order to compare object references and not just their values. Comparing just values wouldn't guarantee that they are identical because primitive types such as strings or integers aren't passed by reference by default.

There are two operators that use a similar principle. These are materialize() and dematerialize().

The first one takes each value, wraps it with a notification object, and re-emits it as a typical onNext signal. This includes error and complete signals as well. These are wrapped and re-emitted like any other value, and after that a complete signal is sent.

This means we can...