blinry on Nostr: nprofile1q…atzsc I want to support different kinds of connections, which use ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqaff84v8ky3pyrnms23wlzjnzuurxjwewprzlf63h8evu5ctm7c2qvatzsc (nprofile…tzsc) I want to support different kinds of connections, which use different types as input and output (for example, some might use a byte stream, some "file watcher events").
Right now, I also made the "data" type in the Input/Output an enum to support different subtypes. But then the core needs to make sure the data type is valid every time.
Do you see an approach to "plug" different connection types to the core in a modular, extensible way? Again, maybe there's some prior work?
Right now, I also made the "data" type in the Input/Output an enum to support different subtypes. But then the core needs to make sure the data type is valid every time.
Do you see an approach to "plug" different connection types to the core in a modular, extensible way? Again, maybe there's some prior work?