Wrote up a (longish) question on StackOverflow abo...

# kotlin-native

[jk2018]

Wrote up a (longish) question on StackOverflow about DetachedObjectGraph (keeping a resource open in a separate thread and sending messages to it), if anyone is inclined to take a peek: -->

[jk2018]

https://stackoverflow.com/questions/59865133/in-kotlin-native-how-to-keep-an-object-around-in-a-separate-thread-and-mutate

[Dominaezzz]

I'll have a go

[jk2018]

Thanks! Hmm, I'm not totally following. Can you elaborate on how you'd use the atomicref? When would the atomic ref change? Also, if I froze the Logger, then I could just pass that into the worker. The point of DOG in my implementation was to keep the Logger mutable ( in my case e.g
to close the file in the end, but the logging+file is really just an example).

[Dominaezzz]

I'm basically saying you should hide the mutability inside the class.

[Dominaezzz]

The atomic ref would change everytime you attach the DetachedObjectGraph , since you'll have to create a new one.

[jk2018]

i see. so with each call to "log", I'd attach it, log, and then create a new DOG, and set it as the ref

[jk2018]

hiding the mutability: yeah that makes sense.

[jk2018]

Just stumbled across this: https://github.com/ktorio/ktor/blame/master/ktor-client/ktor-client-curl/posix/src/io/ktor/client/engine/curl/CurlProcessor.kt uses '@ ThreadLocal'...

[jk2018]

I still wonder what a good usecase for DetachedObjectGraph is. Probably more longer running worker jobs ... Anyways. I guess I was looking for some nice API like a Worker where one can pass in a mutable state. Or something with a constructor where a mutable object could be created. Seems like the idea is that Worker + private vars tagged as ThreadLocal is all we need, and these "nasty" implementation details can/should just be hidden away.

[jk2018]

My experience as someone who's not terribly experienced with concurrency / native dev was quite confusing. I think the problem was that I expected APIs to exist that would handle situations like this in a way that feels less hacky.

[jk2018]

Thx @kpgalligan for your response! Have a little follow up for you on SO.

[kpgalligan]

Updated

[kpgalligan]

I’m working on something like this for Stately, but with the new coroutines rather than Worker directly (but could be with Worker)

[jk2018]

Thanks for sharing your solution!