General HTTP push message broadcast

Open
#110 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby
Domain
backend, frontend

Research direction

Start by reading the existing Comet infrastructure and the IDE plugin's message-receiving path; the issue names no files or tests. Define the sending UI, delivery and display behavior, and archival boundary, then verify that an open IDE receives and displays a broadcast without requiring message storage.

Written by the indexing model from the issue text.

Description

easy enhancement tmc-legacy-course

It would be nice to be able to notify all users with open IDEs about impending downtime, deadlines, newly discovered problems etc. Implement an UI for sending messages via the existing Comet infrastructure and have the IDE plugin receive and display them. No need to store the messages except for archival purposes.

Dominant language
Ruby
Stars
51
Forks
42
Avg merge
1h 27m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from testmycode/tmc-server

All issues in testmycode/tmc-server

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.