|Re: Protocol message specifications [message #1797515 is a reply to message #1797514]
||Thu, 01 November 2018 02:42
| Charles Rivet
Registered: May 2014
What you describe is a concept that was often requested in legacy tooling: the concept of a cable the can contain multiple connectors, each with their own protocol. It was discussed as a potential addition to the language, but it was never assigned to an MVP - mostly a matter of prioritization where parity with legacy tooling was primordial.
However, you could define a protocol that would do what you want by, for example, have a "forward" property that would specify on which port the message would be forwarded. This means that, on reception, it would process this (or these) elements to be forwarded to their final destination. You may still have to handle synchronisation in some way, as the semantics of the state machines will still process one message, to completion, at the time.
Powered by FUDForum
. Page generated in 0.04071 seconds