Backpressure Mitigation

Open
#675 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reading the referenced issues #574, #573, and #653, then inspect how the project currently uses standard JavaScript websockets for client/server communication. The work is complete when file and form-data serialization can handle backpressure transparently, with template tags automating the behavior where possible.

Written by the indexing model from the issue text.

Description

priority-3-low type-revision
Current Situation

We currently use standard JavaScript websockets for client/server communication. The downside of this is that they have no method of handling backpressure, which will become a realistic issue once we begin serializing file content and other form data.

Reference

Proposed Actions

Handle backpressure elegantly, such as through websocket stream libraries.

This ideally should be invisible from a user's perspective, so we want to automate this through template tags when possible.

Reference

Dominant language
Python
Stars
8.1k
Forks
332
No merged PRs in 30d

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.

More from reactive-python/reactpy

All issues in reactive-python/reactpy

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.