Closed nickkuijpers closed 4 years ago
In order to keep this repository focused on bug reports, we auto-close feature requests and requests for help. Feel free to post your feature requests so others can discuss and add reactions. We'll keep an eye on them for later planning.
This would be very helpful. It is kinda of strange to see the screen flashing every time the interval is hit. Services like Sentry also manage to implement polling without refreshing the entire page.
As this approach requires a web socket server, I think this would be better as a third-party package.
It makes sense given how this was implemented as polling instead of socket notifications.
Considerations for a third-party package:
beyondcode/laravel-web-sockets
)laravel-echo
via npm.laravel-echo
on the frontend I dont think the polling is the issue, i think the issue is that whenever there is no new data, the list gets refreshed. If we can disable refreshing the list when there is no new data received, the problem will mostly disappear.
If we use websockets, the same issue will occur, as the websockets gives us new information to display like the polling does.
The problem with that approach is the loading spinner is visible while the network request is active. The front-end would not be able to determine whether the loadmask (flash) should be displayed based on data it hasn't received yet.
The solution to this problem is to re-render the UI when the server broadcasts new data to it via web sockets.
It's something I might look into building in the next month or so.
Ah i understand, thank you for the explanation.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
The polling feature is very nice, thank you.
What would be nice is that whenever the data did not change in the database, we are not re-rendering the resources so we don't see a flash screen of reloading the resources.