reactive-python / reactive-python/reactpy

Use Socket.io instead of Websockets

Open
#775 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

priority-3-low type-investigation
Dominant language
Python
Stars
8.1k
Forks
332
PR merge metrics
No merged PRs in 30d

Description

Current Situation

Currently, IDOM does not fallback to keep-alive HTTP persistent connections in the event that Websockets are not supported.

Proposed Actions

Utilize replace Websocket connections with the Socket.io API, which fills in this gap.

We will need to use python-socketio for compatibility, likely the same way they do with Tornado.

Related issues
  • #581
  • #525

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by reviewing the existing Websocket implementation and related issues #581 and #525; the issue does not name files or tests. Compare the proposed python-socketio approach with the Tornado integration, then define how unsupported Websockets should fall back to persistent HTTP connections and how completion will be tested.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, python
Domain
backend, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.