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

Non-blocking CURLObservable


In our Reddit reader app, we download data from a remote API using PHP's cURL. Even when using its asynchronous callbacks, such as CURLOPT_PROGRESSFUNCTION, it's important to keep in mind that curl_exec() is still a blocking call, no matter what options we choose.

This is due to the fact that PHP runs in a single execution thread and when it starts executing curl_exec(), everything else needs to wait until it finishes. It's true that this method might call some callback functions, but if any of them got stuck, for example, in an infinite loop, the curl_exec() function would never end.

This has serious implications for the actual responsiveness of our Reddit reader. While CURLObservable is downloading data, it doesn't respond to any user input, which is probably not what we want.

When we talked about IntervalObservable and how it's able to keep the desired interval very precisely, we didn't mention that this is, in fact, a type of situation it can't handle.

Let's make...