Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal to introduce SubSystems #154

Open
davesmith00000 opened this issue Dec 3, 2022 · 0 comments
Open

Proposal to introduce SubSystems #154

davesmith00000 opened this issue Dec 3, 2022 · 0 comments

Comments

@davesmith00000
Copy link
Member

This is just a placeholder so that I don't forget.

Note that this isn't quite the same as an Indigo subsystem, although I think you could build something like that on top of this.

It is sometimes desirable to have a long running stream that is outside of the main Tyrian stream, and that has a different use-case to a Sub.

An example of this might be that the Tyrian / Indigo bridge could be rewritten to use an fs2 stream that takes in the usual Msg's and pipes the results back into the main runtime without needing to have a lump of mutable state lying around making the place untidy.

This maintains the decoupling that we aim for in the TEA pattern, but allows long lived processes and communication bridges that might consume and produce messages at uneven rates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant