I have event loops in different languages in different threads of the same process. I'd like them to be able to wake one another up in a cross-platform way. What's my simplest option? I'm currently at: touch a file and listen for fs events on it.
-
-
Replying to @peidran
I feel like the answer is going to vary dramatically depending on the specific languages you're working with. And which platforms you're actually going to support. And your latency/security/maintainability needs. Or does that dodge the question?
1 reply 0 retweets 0 likes -
Replying to @internetmicah
Well, portability is a goal. The platforms are macos, ios, android, and eventually windows. The languages are rust and the platform languages.
1 reply 0 retweets 0 likes -
Replying to @peidran
Do they have to sleep/wake/listen to each other? Like is their state really so precious? Whenever I run into a situation like this, I try to make one language's components as simple as possible and let the other launch it as a new process when needed.
1 reply 0 retweets 0 likes
The simplest thing might to start a new thread that calls into Rust from the host language and Rust just blocks.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.