I am trying to hook communication of 10 iPad's with one iPad.
MCBrowserViewController launches a view controller which will allow to select the Invitees.
It say's "Choose 1 to 7 invitees". As soon as I select One iPad in the network, it says "Choose up to 6 more invitees".
So, is the communication limited to 7 device's? How can will I be able to add 3 other devices? Is the limit related only to MCBrowserController?
No device can be connected to more than seven other devices at the same time. The limit is related to bluetooth, not MCBrowserViewController . In order to connect 10 iPads, you will need to create a chain or a tree of devices.
By constructing a chain of connected iPads I have successfully connected 12 devices. Sending messages down the chain is still reasonably fast. A binary tree of connections is better as you end up with shorter chains but managing those connections is challenging to say the least.
Related
For screen sharing, whenever we invoke navigator.mediaDevices.getDisplayMedia() we need to select the screen that we wish to share, before the streaming can be started. This works fine if it is one to one sharing.
But if I am doing 1 to many screen sharing, we have to create a separate WebRTC connection to each peer. The problem is, if I have 5 peers, I have to select the screen 5 times because every time I call getDisplayMedia() for different peer, it will requires me to select the screen again.
There is no need to call getDisplayMedia multiple times, you can add the track/stream from the first getDisplayMedia call to more than one peerconnection.
See https://webrtc.github.io/samples/src/content/peerconnection/multiple/ for a sample illustrating this. There is only a single call (to getUserMedia in this case)
I am creating a .Net Project on which it monitors a specific data of devices via Modbus communication. I created a form for each devices connected to it, and for each form I added atleast 4 server-based timers from System.Timers.timers class, these 4 timers are the one who manage the communication between devices. Now my question is, since each form corresponds to 1 device, and 1 form has 4 Timers which is running background, my concern is, what If I have multiple device to monitor? let say 50 devices? So it mean I need to run atleast 200 timers at my project right? Does a .net project can accomodate that amount of Timers?
There is only the limit of your hardware (CPU, RAM, ...). So, when using multiple timers, which have the same delay think about using one timer, but do all the desired actions in that one tick to decrease your RAM usage.
I have a peer to peer videoconference app using simpleWebRTC and signalmaster for signaling. When more than 4 users connects the stress it causes on the network and the TURN server is too big, so I was thinking, is it possible to implement a MCU in this case? What would it take to do it?
For more than 4 participants, full mesh (connecting each participant with everyone else peer-to-peer) is impractical. If there are n participants, then each of them needs to have n - 1 outgoing and n - 1 incoming video streams, which quickly saturates the bandwidth, especially on mobile.
An SFU, for example Janus, forwards packets between call participants. The advantage of the SFU for group calls is that each participant needs to push their video stream only once - to the SFU - which then forwards it to everyone else. There are still n - 1 incoming streams for each participant though.
An MCU is capable of combining multiple video streams into one, so each participant ends up with 1 outgoing video stream and 1 incoming composite video stream. To produce a composite video stream out of n - 1 individual ones, an MCU needs to re-encode video in realtime, which makes it a CPU hog.
I would suggest giving Janus (SFU) a try first and seeing how that works for you.
I am looking for a stack allowing to connect several hundred devices,
Openthread has max numbers of hopes equal 16.
Is it possible to extend that number to have 300 devices connected sequentially?
What are requirements to the chip in this case if possible or what limits the max number of connected routing devices?
The Thread Protocol Specification currently has a limit of 15 hops between routers (or 17 hops between end devices). It is not possible to connect hundreds of devices sequentially. At the same time, the Thread Protocol does connecting hundreds of end devices to each router. However, in most practical cases, the number of end devices a router supports is determined by its memory resources.
Auto matching works fine on a wifi connection using
[[GKMatchmakerViewController alloc] initWithMatchRequest:matchRequest];
However, when I switch both devices to use the cellular data connection then the match won't get created. It is just stuck looking for match "forever". Any ideas on what would be causing that? Is that as designed from Apple's matchmaking algorithm.