Binh Duong’s Post

🚀 Exciting Update from Our Decentralized Media Server Open Source Project We are thrilled to announce that our open-source decentralized media server project is currently undergoing a significant phase of improvement: refactoring. This initiative involves a comprehensive overhaul of our entire media server and network stack, integrating advanced sans-io-runtime principles to enhance performance and scalability. Performance Boost: By adopting sans-io-runtime, we are optimizing our media server and network stack to operate more efficiently, ensuring smoother and faster operations for all users. Scalability Enhancement: This refactor aims to bolster our infrastructure's ability to handle increased demands, ensuring robust performance under varying load conditions. Feature Status - Successfully Implemented: 🚀 Cluster Room & Peer: 🚀 Simulcast & SVC: Support WebRTC Simulcast (VP8, H264) and SVC (VP9) - 🚀 Whip Protocol: 🚀 Whep Protocol: 🚀 WebRTC-SDK Protocol: 🚀 Gateway External: 🚀 We deeply appreciate your continued support and eagerly anticipate sharing more updates as we continue to advance with these enhancements. Stay tuned! https://lnkd.in/gTC9wQ2U #OpenSource #MediaServer #Refactoring #Innovation #Performance #Scalability

This article explains how to create a webhook server to handle ImagePolicy validation and the behaviour of the ImagePolicy webhook, including the rules section that defines API operations and resources to intercept. More: https://lnkd.in/gxAuwdbZ

HTTP status codes HTTP status codes are standardized responses from a server that indicate the outcome of a client’s request. These codes, categorized into five classes, provide essential information about the request’s success or failure. https://lnkd.in/d84CnJu9

HTTP 1.1... Going back to basics. I actually thought I knew the basics. Turns out there are other allowed methods besides GET, PUT, POST, PATCH, DELETE, and OPTIONS like: - HEAD: same as GET with no response - CONNECT: establish a tunnel to the destination server - TRACE: request an application-level loop-back (loop-backs are often used to test the quality of a signal path for errors, or to debug physical connection issues), where the server responds almost the same message that it received Also, apparently, the minimum methods a general purpose HTTP server must support are GET and HEAD. If you found that interesting, I invite you to explore more of its documentation. This is the section where I got the above information: https://lnkd.in/gX9X2M4A

Got a small-mid sized #WebRTC deployment? Quick: ❓ What’s the average time a user spends in a meeting/call? ❓ How many users on every meeting? ❓ How many minutes run through your servers every month? ❓ Where are your users joining from around the globe? 👉 If you don’t know the answers to some of these questions then how are you going to scale up your operations? Let alone optimizing it for your existing users… With watchRTC by Cyara you can get the answers to the above really quickly (and it isn’t even what we do) The purpose of watchRTC is to give you the observability (#O11y) you need around your users and your service quality - so you can improve things Check it out! https://lnkd.in/dPF2X69h