[Feature Request] Add support for ws.send_event to a clientside EventBus

Abierto
#3,981 2 comentarios 0 reacciones 1 asignado Ver en GitHub

@T4rk1n ya está trabajando en esto.

Desde el 16/9/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

enhancement P3 size: 10+

The persistent ws callbacks really are great! But I'm missing one feature, the ability to send data directly to clientside JS code.

Is your feature request related to a problem? Please describe.
I have persistent ws-callbacks that sends updates with ws.set_props. Some of the updates needs to run plain JS code (I'm modifies a SVG in realtime based on ws updates)

Describe the solution you'd like
It would be great if the websocket update also could write to an eventbus that js-code can hook on to and listen to.

Describe alternatives you've considered
I've been exploring sending updates via a dcc.Storage and have a clientside callback that act on changes on the dcc.Storage but, this have limitations in rates, if I send updates (with ws.set_props) too frequently some messages are lost, the clientside callback never gets fired. Now we have a asyncio.sleep(0.1) to allow some time for the clientside to pick up the changes. The best solution here would be a channel directly to the JS-code.

Lenguaje dominante
Python
Estrellas
24.4k
Forks
2.3k
Merge medio
2 d 7 h
PR fusionados (30 d)
13

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de plotly/dash

Todos los issues de plotly/dash

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.