Tagging clients in SSE
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start with the SSE example referenced in the issue and inspect how clients are created and how broadcasts are sent. The issue names no file or test; clarify the desired client identifier and selective-delivery behavior before determining what implementation and verification would count as done.
Written by the indexing model from the issue text.
Description
I am not sure if this is right repo to file an issue. So, if I need to move to actix-web-lab then do let me know.
In example there is code to create new client and broadcast message to all clients. Is there any way to I can attach unique id to clients? So, at the time of broadcast I can pick and choose clients where I need to send message. Any pointers would be really useful. Let me know if my question is not clear.
- Dominant language
- Rust
- Stars
- 4k
- Forks
- 812
- Avg merge
- 6h 21m
- Merged PRs (30d)
- 39
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from actix/examples
-
new-example
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
new-example
Difficulty 5/5 Over a week Newbie friendliness 18/100
actix/examples#641 · 1 reaction ·
Maintainers usually reply within 1 day
-
Streaming responses (from an AsyncWrite)May be free again @AraMinjibir claimed this 119 days ago, and no pull request is open. Opengood first issue new-example
Difficulty 4/5 3-5 days Newbie friendliness 48/100
actix/examples#570 · 6 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
actix/examples#465 · 2 comments ·
Maintainers usually reply within 1 day
-
good first issue improvement
Difficulty 3/5 1-2 days Newbie friendliness 25/100
actix/examples#410 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aws/aws-emulator#30 · 1 comment ·
-
tormach-plasma refusal text with no machine reads "no machine is not declared a plasma machine"Openarea:post bug effort:low P2 source:agent
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Chat images never show without ImageMagick: ffprobe fallback uses an option string ffprobe 9 rejectsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
eliasstravik/herdr-projects#1011 ·
-
design-data-spec
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
adobe/spectrum-design-data#1744 ·
Maintainers usually reply within 1 day