[sequenceDiagram] How about implementing support for broadcast messages?
See original GitHub issueHello,
I love mermaid, is pretty straightforward and I use in most of my projects. But there is a feature that I miss which is broadcast messages (useful for events) in the Sequence Diagrams.
I can help you with that, if you do not have time for it, but I’m just asking if this make sense.
I have thought about an operator like <->
<<->>
or even <-->
and <<-->>
respecting the same syntax for the usual arrows.
Any thoughts about it?
Thank you!
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
How to implement broadcast messages - SourceForge
All I know is that I have just such a system that I am trying to represent, and I have to resort to...
Read more >Chapter 2, Section 2.4-2.5 - ece.ufrgs
The vast majority of sequence diagram messages are peer-to-peer. That is, one object transmits a specific message and one object receives it. Broadcast...
Read more >applying broadcasting/multicasting/secured
Figure 10 – Sequence diagram: starting unicast conversation . ... choose to multicast or broadcast the message to find agents on service. In...
Read more >Instructions and Examples - SequenceDiagram.org
Failure Messages are created by using x to denot the arrow head, examples: ... Delete only the else (else is only supported inside...
Read more >Broadcast or a Multicast message in a sequence diagram
I think it does not help to read and maintain the source file. I saw also that it allows to have different messages...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @IOrlandoni, not yet, but I pretend to take a look in the weekend.
Looks good! I will add this issue to the 8.2.0 project and assign to you.