From a client perspective, an actor will simply be a send channel. But from an implementation standpoint, we are allowed to tinker with how our actor behaves.
- Title Page
- Copyright and Credits
- Packt Upsell
- Contributors
- Preface
- Hello, Concurrent World!
- Coroutines in Action
- Downloading and installing Android Studio
- Creating a Kotlin project
- Adding support for coroutines
- Android's UI thread
- Creating a thread
- Adding networking permissions
- Creating a coroutine to call a service
- Adding UI elements
- Displaying the amount of news that were processed
- Using a UI dispatcher
- Creating an asynchronous function to hold the request... or not
- Summary
- Life Cycle and Error Handling
- Suspending Functions and the Coroutine Context
- Improving the UI of the RSS Reader
- Suspending functions
- The coroutine context
- More about contexts
- Summary
- Iterators, Sequences, and Producers
- Channels - Share Memory by Communicating
- Thread Confinement, Actors, and Mutexes
- Atomicity violation
- Thread confinement
- Actors
- Mutual exclusions
- Volatile variables
- Atomic data structures
- Actors in action
- Adding the label to the UI
- Creating an actor to use as a counter
- Increasing the counter as results are loaded
- Adding a channel so that the UI reacts to updates
- Sending the updated value through the channel
- Updating the UI on changes
- Testing the implementation
- Extending the actor to allow for resetting the counter
- Resetting the counter upon new searches
- Summary
- Testing and Debugging Concurrent Code
- The Internals of Concurrency in Kotlin
- Other Books You May Enjoy
More on actor interaction
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.