When you say processing is done on the client side, would that include compute-intensive tasks such as applying filters, gesture recognition, H.264 encoding/decoding, image de-noising, etc.?
Additionally, you mentioned that "they set up the client to use TCP, HTTPS, and HTTP as a fallback for consistent user experience".
-What use cases or scenarios would have TCP be the fallback for UDP to maintain consistent user experience?
Great, succinct article by the way! Just how I love it--start simple, then dive into the details thru progressive discovery.
Excellent. It's clear, concise and informative! Thank you 🙌
appreciate the feedback, Mindi. Thank you
A very useful article with valuable information. A lot is happening behind the scenes of our Zoom meetings. So, are meetings end-to-end encrypted? 😄
yes according to the their documents: https://explore.zoom.us/docs/doc/Zoom%20Encryption%20Whitepaper.pdf
According to their guide, E2EE should be activated by the user explicitly as it is not enabled by default. for more information: https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0065408
interesting.
Coool 😁
thanks
When you say processing is done on the client side, would that include compute-intensive tasks such as applying filters, gesture recognition, H.264 encoding/decoding, image de-noising, etc.?
Additionally, you mentioned that "they set up the client to use TCP, HTTPS, and HTTP as a fallback for consistent user experience".
-What use cases or scenarios would have TCP be the fallback for UDP to maintain consistent user experience?
Great, succinct article by the way! Just how I love it--start simple, then dive into the details thru progressive discovery.
That was very interesting. Do zoom use some open source package to help with the video side or is it all proprietary?