blinry on Nostr: nprofile1q…atzsc And secondly, how would you model a scenario with many connected ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqaff84v8ky3pyrnms23wlzjnzuurxjwewprzlf63h8evu5ctm7c2qvatzsc (nprofile…tzsc) And secondly, how would you model a scenario with many connected "clients" (like a chat server)?
Currently, I'm trying to make the core free of IO, like you often suggest, and feed events like this to it:
enum Event {
Connect(id, type)
Input(id, data)
Disconnect(id)
}
The core then returns "actions" like this:
Output(id, data)
A "shell" then drives this interface. So far so good, but:
Currently, I'm trying to make the core free of IO, like you often suggest, and feed events like this to it:
enum Event {
Connect(id, type)
Input(id, data)
Disconnect(id)
}
The core then returns "actions" like this:
Output(id, data)
A "shell" then drives this interface. So far so good, but: