Skip to content

Use one websocket per client #231

Open
@Archmonger

Description

@Archmonger

Current Situation

The initial handshake of a websocket connection can cause additional latency. It's sometimes more performant to utilize only one websocket connection per client.

Proposed Actions

Refactor consumer.py and our client code to utilize a single websocket per client. This will likely require changing our websocket's URL routing schema.

We might want to make this option configurable via REACTPY_SHARED_WEBSOCKET, since the old behavior has the potential to be more performant when using multiple ASGI workers.

Alternatively, if this feature is optional then perhaps this might be better developed as a separate SharedReactPyConsumer websocket.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy