Feature proposal: broadcast after patch
See original GitHub issueHey everyone & @colyseus/gladiators
I have a use-case where a broadcast
message needs to arrive AFTER the state has been patched in the client-side. I’m thinking how the API for this should look like.
As broadcast
currently allows passing options along with it (as options.except
: https://github.com/colyseus/colyseus/issues/136), I’m thinking on enabling this now:
this.broadcast(data, { delayed: true });
A “delayed” broadcast means it will be sent only after the patch has been sent. I’m afraid this is not intuitive enough.
To be more intuitive, we could use afterPatch
, but it looks weird:
this.broadcast(data, { afterPatch: true });
What are your thoughts? Thanks!
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Broadcast group (distribution list) - Delta.Chat
Introduce Experimental Broadcast Groups Fix for speedup chatlist #1602 Many ... Broadcast messages (for later version after 1.0 release) Feature Proposal.
Read more >Programmatic Guaranteed deals - Display & Video 360 Help
A request for proposal (RFP) is a document sent from media planners like you to inventory providers that request media (inventory) to purchase...
Read more >2022 Broadcasts - NJ.gov
2022 Broadcasts · December 21 · December 14 · December 7 · December 1 · November 30 · November 23 · November 16...
Read more >Film Proposal Template: Move your Film into Development
A Film Proposal is a 1-page document to pitch your idea to key team members and hand out at film markets. What your...
Read more >Issues workflow - GitLab Docs
To create a feature proposal, open an issue on the issue tracker. In order to help track the feature proposals, we have created...
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 Free
Top 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
I think if you’re not going to offer analogs like
beforePatch
, then it doesn’t make sense to useafterPatch
. I would be explicit:delayUntilFirstPatch
ordelayUntilAfterFirstPatch
or the like.Thanks for the explain. I got the point.