Working professionally with WebRTC and WebSockets can reveal you a world of wonders that you weren't previously accustomed to using plain web technologies. That dreadful moment when the boss tells you:
- It doesn't work
And you need to scramble to figure out what's wrong, what's the vector? Is it WebRTC? Is it WebSockets? Is it the mobile device? The Network they are on? Enough is enough so during the NodeKO hackathon weekend i implemented www.check-connectivity.com a website that will reliably report connectivity and the browser's information. Hell it can even determine if you are behind a NAT!
It's been a while since NodeKO and i've been hard at work integrating the API to our support forums so with each new ticket a full report of the connectivity and browser status is attached. Today i'd like to share this invaluable tool with you and hopefully get some feedback on how this tool can help you... Enjoy:
- It doesn't work
And you need to scramble to figure out what's wrong, what's the vector? Is it WebRTC? Is it WebSockets? Is it the mobile device? The Network they are on? Enough is enough so during the NodeKO hackathon weekend i implemented www.check-connectivity.com a website that will reliably report connectivity and the browser's information. Hell it can even determine if you are behind a NAT!
It's been a while since NodeKO and i've been hard at work integrating the API to our support forums so with each new ticket a full report of the connectivity and browser status is attached. Today i'd like to share this invaluable tool with you and hopefully get some feedback on how this tool can help you... Enjoy:
http://www.check-connectivity.com