https://kotlinlang.org logo
Channels
100daysofcode
100daysofkotlin
100daysofkotlin-2021
advent-of-code
aem
ai
alexa
algeria
algolialibraries
amsterdam
android
android-architecture
android-databinding
android-studio
androidgithubprojects
androidthings
androidx
androidx-xprocessing
anime
anko
announcements
apollo-kotlin
appintro
arabic
argentina
arkenv
arksemdevteam
armenia
arrow
arrow-contributors
arrow-meta
ass
atlanta
atm17
atrium
austin
australia
austria
awesome-kotlin
ballast
bangladesh
barcelona
bayarea
bazel
beepiz-libraries
belgium
benchmarks
berlin
big-data
books
boston
brazil
brikk
budapest
build
build-tools
bulgaria
bydgoszcz
cambodia
canada
carrat
carrat-dev
carrat-feed
chicago
chile
china
chucker
cincinnati-user-group
cli
clikt
cloudfoundry
cn
cobalt
code-coverage
codeforces
codemash-precompiler
codereview
codingame
codingconventions
coimbatore
collaborations
colombia
colorado
communities
competitive-programming
competitivecoding
compiler
compose
compose-android
compose-desktop
compose-hiring
compose-ios
compose-mp
compose-ui-showcase
compose-wear
compose-web
confetti
connect-audit-events
corda
cork
coroutines
couchbase
coursera
croatia
cryptography
cscenter-course-2016
cucumber-bdd
cyprus
czech
dagger
data2viz
databinding
datascience
dckotlin
debugging
decompose
decouple
denmark
deprecated
detekt
detekt-hint
dev-core
dfw
docs-revamped
dokka
domain-driven-design
doodle
dsl
dublin
dutch
eap
eclipse
ecuador
edinburgh
education
effective-kotlin
effectivekotlin
emacs
embedded-kotlin
estatik
event21-community-content
events
exposed
failgood
fb-internal-demo
feed
firebase
flow
fluid-libraries
forkhandles
forum
fosdem
fp-in-kotlin
framework-elide
freenode
french
fritz2
fuchsia
functional
funktionale
gamedev
ge-kotlin
general-advice
georgia
geospatial
german-lang
getting-started
github-workflows-kt
glance
godot-kotlin
google-io
gradle
graphic
graphkool
graphql
graphql-kotlin
graviton-browser
greece
grpc
gsoc
gui
hackathons
hacktoberfest
hamburg
hamkrest
helios
helsinki
hexagon
hibernate
hikari-cp
hire-me
hiring
hongkong
hoplite
http4k
hungary
hyderabad
image-processing
india
indonesia
inkremental
intellij
intellij-plugins
intellij-tricks
internships
introduce-yourself
io
ios
iran
israel
istanbulcoders
italian
jackson-kotlin
jadx
japanese
jasync-sql
java-to-kotlin-refactoring
javadevelopers
javafx
javalin
javascript
jdbi
jhipster-kotlin
jobsworldwide
jpa
jshdq
juul-libraries
jvm-ir-backend-feedback
jxadapter
k2-early-adopters
kaal
kafka
kakao
kalasim
kapt
karachi
karg
karlsruhe
kash_shell
kaskade
kbuild
kdbc
kgen-doc-tools
kgraphql
kinta
klaxon
klock
kloudformation
kmdc
kmm-español
kmongo
knbt
knote
koalaql
koans
kobalt
kobweb
kodein
kodex
kohesive
koin
koin-dev
komapper
kondor-json
kong
kontent
kontributors
korau
korean
korge
korim
korio
korlibs
korte
kotest
kotest-contributors
kotless
kotlick
kotlin-asia
kotlin-beam
kotlin-by-example
kotlin-csv
kotlin-data-storage
kotlin-foundation
kotlin-fuel
kotlin-in-action
kotlin-inject
kotlin-latam
kotlin-logging
kotlin-multiplatform-contest
kotlin-mumbai
kotlin-native
kotlin-pakistan
kotlin-plugin
kotlin-pune
kotlin-roadmap
kotlin-samples
kotlin-sap
kotlin-serbia
kotlin-spark
kotlin-szeged
kotlin-website
kotlinacademy
kotlinbot
kotlinconf
kotlindl
kotlinforbeginners
kotlingforbeginners
kotlinlondon
kotlinmad
kotlinprogrammers
kotlinsu
kotlintest
kotlintest-devs
kotlintlv
kotlinultimatechallenge
kotlinx-datetime
kotlinx-files
kotlinx-html
kotrix
kotson
kovenant
kprompt
kraph
krawler
kroto-plus
ksp
ktcc
ktfmt
ktlint
ktor
ktp
kubed
kug-leads
kug-torino
kvision
kweb
lambdaworld_cadiz
lanark
language-evolution
language-proposals
latvia
leakcanary
leedskotlinusergroup
lets-have-fun
libgdx
libkgd
library-development
lincheck
linkeddata
lithuania
london
losangeles
lottie
love
lychee
macedonia
machinelearningbawas
madrid
malaysia
mathematics
meetkotlin
memes
meta
metro-detroit
mexico
miami
micronaut
minnesota
minutest
mirror
mockk
moko
moldova
monsterpuzzle
montreal
moonbean
morocco
motionlayout
mpapt
mu
multiplatform
mumbai
munich
mvikotlin
mvrx
myndocs-oauth2-server
naming
navigation-architecture-component
nepal
new-mexico
new-zealand
newname
nigeria
nodejs
norway
npm-publish
nyc
oceania
ohio-kotlin-users
oldenburg
oolong
opensource
orbit-mvi
osgi
otpisani
package-search
pakistan
panamá
pattern-matching
pbandk
pdx
peru
philippines
phoenix
pinoy
pocketgitclient
polish
popkorn
portugal
practical-functional-programming
proguard
prozis-android-backup
pyhsikal
python
python-contributors
quasar
random
re
react
reaktive
realm
realworldkotlin
reductor
reduks
redux
redux-kotlin
refactoring-to-kotlin
reflect
refreshversions
reports
result
rethink
revolver
rhein-main
rocksdb
romania
room
rpi-pico
rsocket
russian
russian_feed
russian-kotlinasfirst
rx
rxjava
san-diego
science
scotland
scrcast
scrimage
script
scripting
seattle
serialization
server
sg-user-group
singapore
skia-wasm-interop-temp
skrape-it
slovak
snake
sofl-user-group
southafrica
spacemacs
spain
spanish
speaking
spek
spin
splitties
spotify-mobius
spring
spring-security
squarelibraries
stackoverflow
stacks
stayhungrystayfoolish
stdlib
stlouis
strife-discord-lib
strikt
students
stuttgart
sudan
swagger-gradle-codegen
swarm
sweden
swing
swiss-user-group
switzerland
talking-kotlin
tallinn
tampa
teamcity
tegal
tempe
tensorflow
terminal
test
testing
testtestest
texas
tgbotapi
thailand
tornadofx
touchlab-tools
training
tricity-kotlin-user-group
trójmiasto
truth
tunisia
turkey
turkiye
twitter-feed
uae
udacityindia
uk
ukrainian
uniflow
unkonf
uruguay
utah
uuid
vancouver
vankotlin
vertx
videos
vienna
vietnam
vim
vkug
vuejs
web-mpp
webassembly
webrtc
wimix_sentry
wwdc
zircon
Powered by
Title
r

ribesg

03/25/2019, 10:14 AM
How would I implement a sequence doing HTTP request using the Ktor client? I get an error about restricted suspending functions when using
sequence { }
g

gildor

03/25/2019, 10:16 AM
sequence doesn’t support any kind async events, this is syncronous only abstraction
you can use Channels instead
r

ribesg

03/25/2019, 10:16 AM
Oh, ok
g

gildor

03/25/2019, 10:17 AM
In future you also can use cold streams, when they will be released, for now Channels is the only abstraction for data streams compatible with coroutines
r

ribesg

03/25/2019, 10:26 AM
I’m basically implementing pagination, I don’t know much about channels. Is there an example somewhere on how to use channels for that?
g

gildor

03/25/2019, 10:27 AM
briefly: instead of
sequence { }
use
CoroutineScope.produce { }
r

ribesg

03/25/2019, 10:29 AM
Yeah that’s what I get from those docs. So
send
would not be called until there’s a consumer, right?
g

gildor

03/25/2019, 10:29 AM
Depends on channel type
there are different ones, but this is default one, rendezvous channel, and it works as you described
f

Fredrik Larsen

03/25/2019, 12:43 PM
Sorry to highjack the thread, but you mentioned cold streams. Would they work similar to Rx observables?
g

gildor

03/25/2019, 1:34 PM
@Fredrik Larsen Yes, the main idea is the same, but based on coroutines More details: https://github.com/Kotlin/kotlinx.coroutines/issues/254
f

Fredrik Larsen

03/25/2019, 1:34 PM
Interesting. Thank you @gildor
r

ribesg

03/25/2019, 2:15 PM
@gildor when using a producer, it does one more request than needed because it waits for a
receive
when I call
send
, but when I call
send
I already did the next request. Is there a way to start the next request when
receive
is called, and not before, to prevent downloading potentially useless data?
b

bdawg.io

03/25/2019, 3:03 PM
I'm not entirely sure if
onSend
would get you that. @gildor do you happen to know if
onSend
is only a listener event or if it actually puts an item on the queue as well?
Is there a way to start the next request when
receive
is called, and not before
fun CoroutineScope.loadPages() = produce<List<MyItem>> {
    var currentPage = 1
    while (true) {
        val page = loadPageNum(currentPage)
        if (page.isEmpty()) {
            break;
        }
        // await until item is received
        send(page)
        currentPage += 1
    }
}
r

ribesg

03/25/2019, 3:12 PM
@bdawg.io this does download the next page before it’s needed. Also `onSend`’s prototype is scary
b

bdawg.io

03/25/2019, 3:13 PM
@ribesg I'm not understanding why. Unless you're specifying a capacity on your producer, it should suspend until someone `receive`s it. That's why it's called a Rendezvous channel
I've never used
onSend
haha so I wasn't sure if it'd actually be useful or not lol
r

ribesg

03/25/2019, 3:16 PM
You’re calling loadPageNum before blocking on send
So the page is loaded before we start waiting for someone to consume the page
I don’t want to download it unless something wants it
b

bdawg.io

03/25/2019, 3:21 PM
That sounds like a cold stream. An alternative is to return a
Lazy<ReceiveChannel<YourType>>
and then have your consumer unwrap the value before consuming
val pages by lazy { loadPages() }
pages.consumeEach { ... }
r

ribesg

03/25/2019, 3:25 PM
That doesn’t change anything as we’re still loading one more page than needed.
I totally need a cold stream here it seems, but there’s no such thing right now
b

bdawg.io

03/25/2019, 3:46 PM
Why doesn't it change anything? Only one page is loaded at a time and it doesn't get loaded until first access of the
Lazy
(for above, not until
pages.consumeEach
is called)?
r

ribesg

03/26/2019, 9:11 AM
@bdawg.io I’m not sure how to explain it better, but you always retrieve a page before calling
send
which is the blocking point. So you always have a unused page in memory, which may never be used. Your
lazy
trick only works on the first page.
g

gildor

03/26/2019, 9:11 AM
@ribesg Yes, exactly, this is how hot streams (channels) work and this will be properly solved only by cold streams
r

ribesg

03/26/2019, 9:13 AM
In the meantime, here’s my solution:
interface PageIterator<T> {
        suspend fun next(): List<T>
    }
object : PageIterator<MyType> {

            private var lastReturnedPage = -1
            private var done = false

            override suspend fun next(): List<MyType> {
                if (done) return emptyList()
                val res = doMyHttpRequest(++lastReturnedPage)
                done = lastReturnedPage == res.nbPages - 1
                return res.results
            }

        }
g

gildor

03/26/2019, 9:13 AM
Sure, this is your own solution for this
Actually this problem is described in first and second comment in Cold Streams issue and one of main use cases
r

ribesg

03/26/2019, 9:15 AM
Yes, I know that cold streams are the solution, but I needed an actual real solution for now, not a future one 🙂
g

gildor

03/26/2019, 9:16 AM
It’s not so a future, planned for April, as I heard But I agree, nothing wrong with own case-specific solution, especially if you don’t integrate with other data streams
r

ribesg

03/26/2019, 9:18 AM
A lot of things I need will be out very soon, that’s unfortunate but I need to progress in my implementation
g

gildor

03/26/2019, 9:21 AM
Again, I think it’s completely fine, some kind high level abstraction for streams required only if you have to manage multiple data streams and it may be much more tricky with ad-hoc solution
r

ribesg

03/26/2019, 9:23 AM
Yeah, in my case I just needed a
suspend
next
function doing an Http request, so I did just that. Hopefully I’ll be able to use existing things in the future.