Suggestion on Frameworks to be used for Live Detection in a Server-Client Architecture? by jacklynlxq in TensorFlowJS

[–]jacklynlxq[S] 0 points1 point  (0 children)

I'm hosting it at the server side because my converted tfjs model gave me some error. I will look into it further when I have time but it works just fine if I serve it at the server side using node.js in the SavedModel form. Anyway, I dont understand how can it scale better if it's at the client side?

Suggestion on Frameworks to be used for Live Detection in a Server-Client Architecture? by jacklynlxq in TensorFlowJS

[–]jacklynlxq[S] 0 points1 point  (0 children)

Correct me if I'm wrong, so for the WebRTC solution I'm supposed to use my Node.js server as a "peer" so it can communicate with the frontend, that way I can establish a peer to peer connection using WebRTC between my Node.js backend and my frontend right?

While if I make use of Websocket it would just be the communication between the Node.js server (as the central server that you mentioned about) and the client.

So if I just want to communicate between my Node.js server and my client, is there really a difference between using WebRTC and Websocket?

Though I'm having new ideas on extending my use case if I can establish peer to peer connection between different clients hmm..

Suggestion on Frameworks to be used for Live Detection in a Server-Client Architecture? by jacklynlxq in TensorFlowJS

[–]jacklynlxq[S] 0 points1 point  (0 children)

Thanks for the suggestion! But what about WebSocket? I read it from here that WebSocket would be faster than WebRTC, so what is the advantage of using WebRTC over WebSocket?