Dash OSS/Ent: Push to client

Given someone is looking at a Dash app in their browser, when data updates on the backend, a mechanism to push that data to the frontend.

Think about recreating an example like: https://www.ag-grid.com/ Is this a third class of callback? Duration of time you have the component the callback is connected to displayed on the page? i.e. first-class web-sockets. Imagine the feature where you have two users interacing with a Dash app displaying a grid. One user edits a cell in the grid. That is pushed to the database. The other person is viewing the same grid, and the database update is pushed to the client with no input\/interval polling the server. Think about this architecture of this in today's Dash vs. a Dash where we can hold open a connection?

Please authenticate to join the conversation.

Upvoters
Status

In Review

Board

Libraries

Date

Almost 2 years ago

Author

Nathan Drezner

Subscribe to post

Get notified by email when there are changes.