Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

data dropped between backend and client #124

Open
jamesarm97 opened this issue Feb 19, 2019 · 1 comment
Open

data dropped between backend and client #124

jamesarm97 opened this issue Feb 19, 2019 · 1 comment

Comments

@jamesarm97
Copy link

Is there a limit on how fast you can push data to widgets? I have an app sending port status updates in realtime and I can see all the posts showing on the smashing screen as they come in but on the webclient / desktop, I only get some of the packets to the widget. I even put a counter in the app sending the data to the smashing service and on my browser console log I see gaps in the data. I'm not sure how the backend pushes data to the browser and what those limits may be. I am sending 10 posts to the backend using the old dashing node client and the smashing log seems to show all of them but only get 2-3 of them on the widget when debugging it.

@th3fall3n0n3
Copy link

Same for me, seems like there is a delay between data refresh from browser/smashing.

It wasn't that way in dashing

@kinow kinow added this to the 1.4.0 milestone May 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants