In the `SimplifiedSessionStorage` example on <http...
# ktorm
mp
10/29/2018, 5:39 PMIn the
SimplifiedSessionStoragegetCoroutineContext()reader()CoroutineScope.reader📝 1
✅ 1
d
Deactivated User
10/29/2018, 5:40 PMThat looks like outdated
Deactivated User
10/29/2018, 5:40 PMThere is an intrinsic called
coroutineContextgetCoroutineContextDeactivated User
10/29/2018, 5:41 PMAbout the reader part, let me check
m
mp
10/29/2018, 5:41 PMthat makes much more sense
d
Deactivated User
10/29/2018, 5:41 PMyeah I have still to revisit every single page now that Kotlin 1.3 and kotlinx.coroutines 1.0.0 are released and are stable (and Ktor is almost there)
m
mp
10/29/2018, 5:43 PMwe appreciate the effort put into the docs 🙂
simple smile 1
👌 2
mp
10/29/2018, 5:53 PMMaybe I'm missing something about coroutine scopes (quite plausible) but it seems like this should be attached to the scope of a call, but how would that scope make its way down to this level if it's not passed as an argument to
SessionStoraged
Deactivated User
10/29/2018, 5:56 PMCoroutineScope(<http://Dispatchers.IO|Dispatchers.IO>)Deactivated User
10/29/2018, 5:56 PMNo scope is propagated
Deactivated User
10/29/2018, 5:58 PMso right now it is not attached
m
mp
10/29/2018, 5:59 PMI see. I'm still pretty fuzzy on how best to use scopes, but CoroutineScope(Dispatchers.IO) seems defensible
d
Deactivated User
10/29/2018, 5:59 PMbut it is really necessary that it is attached? Since those I/O stuff should be short and usually request/response, or even long lived
m
mp
10/29/2018, 6:00 PMI'm not really sure
d
Deactivated User
10/29/2018, 6:00 PMbut I don’t have a strong opinion on this either
m
mp
10/29/2018, 6:00 PMI just want the IDE to not be mad at me 😉
d
Deactivated User
10/29/2018, 6:00 PM🙂