Skip to content

New Capability: Reactive Message Handling Flow [Enhancement] #313

Open
@TaviTruman

Description

I'm suggesting this new capability based on a couple of years of developing WPF apps with GE Client capabilities with particular support for MVVM and Semantic-powered process substrates.

Extended the Trinity Networking protocol layer to formally support Reactive Message Handling flow. I am able to implement this capability via the following:

  • Specify Type: Asyn in the TSL
  • Specify Response: int in the TSL * Must do so that we can await the method call!
  • Add new Keyword Reactive with Payload Type
  • Code gen should create IObserver and IObservables in the base class
  • Add formal and stronger API semantics for Publish, Subscribe and extend the Request and Response code generation policy for sold API semantics. Code generation should use Reactive Design patterns for Server and Client-side use.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions