ERnsTL
commented
2 years ago - 1 room = 1 component?
- Everything that is posted into this room is taken as input -> forward on port OUT into flowd network.
- Setting whether framed on unframed messages are expected and what to do with non-wellformed messages (in case of "framed FBP network protocol messages").
- What is the use-case? between flowd components or mainly used between components located in different runtimes? why not just use a TCP socket component?
- Is data history in the room useful/desired?
- Crate: https://docs.rs/matrix-sdk/latest/matrix_sdk/
- or more high-level: https://github.com/8go/matrix-commander-rs/releases
- Example: https://github.com/matrix-org/matrix-rust-sdk/blob/main/examples/getting_started/src/main.rs
- Matrix has a workflow that does not fit well with flowd and FBP
- it synchronizes state on room objects - and does not have flowing data like flowd has.
- it has callbacks to authorize the device
- would need to be input into the matrix component
- Matrix bot is always reader and writer, so has IN+OUT always.
- need to send to Drop if not used
- need "/dev/null" component which never sends anything just to keep the port connected.