You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 17, 2020. It is now read-only.
I was thinking if I can move the server out from device itself and put it on a different server.
I tried to do it but code is too complex, any suggestions or already done code piece would help a ton!
Open for suggestions.
The text was updated successfully, but these errors were encountered:
I'm not sure what you are suggesting. If you mean having the app send the data to a server which does the HTTP part, I'm not sure what good it would do you. The overhead for the HTTP part is pretty low.
Thats what exactly I meant, sending the video frames to a backend server over HTTP or any other protocol, but doesnt wanna handle it on the device itself. As it heats up the device pretty quickly.
What's heating up the device is the camera use and the continuous JPEG compression. You will have to send the data to the server somehow, so you might as well do it via HTTP.
You might be able to move the compression step to the server and send only the raw bitmap, but you would have to come up with your own protocol for this, and the network might not be able to handle dozens of uncompressed bitmaps per second.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I was thinking if I can move the server out from device itself and put it on a different server.
I tried to do it but code is too complex, any suggestions or already done code piece would help a ton!
Open for suggestions.
The text was updated successfully, but these errors were encountered: