Feature Request: Support sending multiple times (reuse Wormhole code)
See original GitHub issueHi, I am thinking if it’s possible for the sender to restart sending when a transaction is done. For example, when you want to deliver a file on sender A to multiple computer B1,B2,B3…Bn
Currently, the magic-wormhole exits when one transaction is done. I have to restart the sender n times and type n different keys on the receivers.
Is it possible to implemented an option like --reuse times
to keep the sender sending when a transaction is done. So that I can type the same receive code on the n servers.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:9 (1 by maintainers)
Top Results From Across the Web
Support sending multiple times (reuse Wormhole code) · Issue ...
Currently, the magic-wormhole exits when one transaction is done. I have to restart the sender n times and type n different keys on...
Read more >Magic-Wormhole Documentation - Read the Docs
The two endpoints are identified by using identical “wormhole codes”: in general, the sending machine generates and displays the code, which must then....
Read more >The Magic-Wormhole API - Read the Docs
The “Wormhole” object provides a secure record pipe between any two programs that use the same wormhole code (and are configured with the...
Read more >E2E-Testing in CI Environment With Testcontainers - Medium
Learn how run E2E tests of multiple microservices in CI environment with Spring Boot and Testcontainers usage.
Read more >Wormhole: How to Play and Rewards | Tower of Fantasy
Enemies' weaknesses will be shown before you enter, so take time to change your current loadout if you have to! Equip Weapons and...
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
I was replying to the comment on March 4, which sounds like it could be about 1:1 session – although I do see that the overall feature-request is about 1:N sessions, approximately.
perhaps introducing an interactive mode … the code is still good only once … but that is one interactive session … keep it open until either side closes their connection.