What is the use case for flows?

# coroutines

[asad.awadia]

What is the use case for flows?

[zak.taccardi]

multiple values over time

[asad.awadia]

For what use case tho?

[zak.taccardi]

are you familiar with RxJava?

[zak.taccardi]

or LiveData<T>

[asad.awadia]

Yes

[zak.taccardi]

that’s the use case

[asad.awadia]

Thats not a use case

[asad.awadia]

A use case is like when a user is typing then you do foobar

[zak.taccardi]

okay

[zak.taccardi]

for a ViewModel to expose a stream of states

[asad.awadia]

Preferably examples on server side than UI side

[zak.taccardi]

it would be represented as Flow<State>

[asad.awadia]

Basics events?

[zak.taccardi]

I don’t do server side dev so I couldn’t tell you

[asad.awadia]

Basically #

[zak.taccardi]

yes, events would qualify

[zak.taccardi]

in any place you would set a listener to receive callbacks for multiple values over time, Flow<T> makes sense

[zak.taccardi]

for a single value, suspend () -> T should be preferred

[asad.awadia]

Hmm i guess that kinda makes sense

[asad.awadia]

Wonder how to use it backend side

[zak.taccardi]

a socket connection?

[zak.taccardi]

(maybe)

[asad.awadia]

How?

[asad.awadia]

Lol

[zak.taccardi]

subscribing to a Flow<T> would create a socket connection containing events of type T

[gildor]

Every stream of events can be represented as Flow:
Server requests, socket connection, database updates, periodical events etc
Essentially everything where you use callbacks that can be called multiple times.
For example check how Spring uses Reactor (which is also reactive library), you can represent whole web service as chain of events where source is request that converted to response event