Noob here. I am very confused with the Cloudflare Calls API. If my interpretation is correct, this i
Noob here. I am very confused with the Cloudflare Calls API. If my interpretation is correct, this is really just an enhanced SFU which simplifies the webrtc relay by only requiring clients to have 1 PC with the SFU. But a custom signaling server implementation is still required, acting as the intermediary, to manage and close tracks/sessions/renegotiations/etc... However, I am likely overlooking something here but the real value with this is for easy integration particularly for high-tenancy media sessions/streams? But given a hypothetical scenario where we are building a native webrtc application, would it not otherwise be cheaper to solution multi-tenancy using only STUN/Signaling (including multiple PC overlayed for each "participant") and then failover to Cloudflare TURN ($0.05/GB, same as Call API) if connection cannot be established? To me, the traditional approach + Cloudflare TURN for NAT/Firewall traversal is the cheapest design?
