Goal:
Realtime data steaming display. The expected behavior is to be able to connect to PusherJS to receive realtime data update from server.
Steps:
Seems like the only way is to use custom component + WebSocket. We are using PusherJS, the current workaround would require extra configuration and setup to manage the data and re-pipe the data to WebSocket.
Not really. Our system use Pusher to broadcast realtime data. Due to the way our system operate, we can't use pull. We are also not storing the realtime data.
We currently do not have any built in integrations for this type of functionality.
You may be able to hack together something using @khill-fbmc's suggestion of running a query to a REST API and have that server serve the data back to the app.
Also a workflow has an exposed trigger URL that could be the recipient of data payloads from a webhook. This could be used to get data and move it to a place where it is accessible by an app query.
Hey all! I still think that a custom component will be your best option here, but it doesn't need to be a super low-level solution. Is there any reason not to build out a pusher-js client that can hook directly into the data stream from your server? I don't know exactly how the library is built, but I have to imagine that it utilizes websockets.
I agree here, PusherJS does use websockets so a custom component would work. It wouldn't need any UI parts, it just needs to emit events for your frontend to know when to update: