####1. Describe Your Issue
While the forum was down, I asked some connectivity questions by email. I want to follow-up with more specifics and get the topic and answers for others to see. From this perhaps documentation updates and feature requests could follow.
My interest is that clients can connect to a skill that provides server capabilities e.g. websockets, udp, http. Obviously provides another way for users to interact with Jibo. I’m particularly interested in devices in the local network.
In the simulator, I can run a simple chat demo using npm socket.io and http (via express for now). The Jibo skill listens on port 3000, my browser connects to the simulator skill and everything works fine. I have game and story feature ideas that include chat.
Question 1: Now on the real robot, would this chat skill work where the skill provides a websocket server?
If not, then it would be useful if these restrictions were documented and the simulator changed to reflect these connectivity restrictions.
I’m also looking at WebRTC - same issue.
Question 2: can we use webrtc on the actual robot? The chromium browser is likely ok, not sure about the restrictions.