06-06-2020, 08:31 PM
(This post was last modified: 06-06-2020, 08:40 PM by Hans Peter Augustesen.)
It is true that JamKazam is so-called peer-to-peer (P2P).
But that fact is not the cause of the problems as such.
The real cause is, as mentioned, "if a remote user had a bad h / w or s / w configuration or network link".
In short: lousy internet connections.
Or the Internet connection is too bad for the current job. As it is mentioned "The more people you connect to at the same time, and the more channels each one has, the more bandwidth everyone needs."
Put another way: there could also be similar problems if JamKazam had not been peer-to-peer
I believe it can/could happen even if Jamkazam did not use a peer-to-peer network model, so to speak.
A general good attitude also helps to avoid making a mess of things - for sure ...
A crappy internet connection can crash a session.
JamKazam recommends maximum 7 participants in a session
According to TEST NETWORK my connection can support 8 participants in a session.
That is a paradox!
But that fact is not the cause of the problems as such.
The real cause is, as mentioned, "if a remote user had a bad h / w or s / w configuration or network link".
In short: lousy internet connections.
Or the Internet connection is too bad for the current job. As it is mentioned "The more people you connect to at the same time, and the more channels each one has, the more bandwidth everyone needs."
Put another way: there could also be similar problems if JamKazam had not been peer-to-peer
I believe it can/could happen even if Jamkazam did not use a peer-to-peer network model, so to speak.
A general good attitude also helps to avoid making a mess of things - for sure ...
A crappy internet connection can crash a session.
JamKazam recommends maximum 7 participants in a session
According to TEST NETWORK my connection can support 8 participants in a session.
That is a paradox!