Hands-On Design Patterns with Kotlin

Hot Observable

Hot Observable is a term we'll use a lot in this chapter, as opposed to cold Observable. All Observable we discussed before was cold. That meant they knew everything that happened from the beginning of time, and each time somebody asked them politely, they could repeat the whole history. Hot Observable only know what happens now. Think of the weather forecast and weather history, for example. The weather forecast is hot—you'll get the current weather, let's say every minute. The weather history is cold–you can get the whole history of weather changes, if you care about it. If you still don't get this concept, don't worry too much. We have half of the chapter ahead of us to cover it.

As you've probably noticed, up until now, ...