My piano teacher recently introduced me to Jamulus, and we successfully used it to play a duet (thanks Jamulus dev community!)
My piano teacher is not technical however (whereas I'm a software engineer), and the whole 'server' thing was a bit of a dark mystery to her. She had in the past used "a friend's server", and seemed amazed I had the magical skills to do it. She was even more astonished that I was running on the same laptop as I was running the client. Note, I only ran the server for the duration of my session.
Anyway, I'm wondering quite what the central server registries are doing that they need to be limited. I found https://github.com/jamulussoftware/jamulus/issues/875 - but didn't think it was appropriate to barge in and ask questions.
My impression was that a central server would only be needed for signalling/discovery in a similar manner to P2P NAT hole punching, but then why the limit? Once the server (that I run) is registered with the Jamulus central servers, and then a remote person has found it - is all further comms direct?
Is there anywhere I can read about this aspect of Jamulus - the documentation on client and server is extensive and very good, but I can't seem to find much about this part.
I essentially want to know what the bottleneck is for the lists, why it would be a few lists of 150 rather than a single discovery server that can handle millions.
Last edit: Marcos Scriven 2021-02-05
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My piano teacher recently introduced me to Jamulus, and we successfully used it to play a duet (thanks Jamulus dev community!)
My piano teacher is not technical however (whereas I'm a software engineer), and the whole 'server' thing was a bit of a dark mystery to her. She had in the past used "a friend's server", and seemed amazed I had the magical skills to do it. She was even more astonished that I was running on the same laptop as I was running the client. Note, I only ran the server for the duration of my session.
Anyway, I'm wondering quite what the central server registries are doing that they need to be limited. I found https://github.com/jamulussoftware/jamulus/issues/875 - but didn't think it was appropriate to barge in and ask questions.
My impression was that a central server would only be needed for signalling/discovery in a similar manner to P2P NAT hole punching, but then why the limit? Once the server (that I run) is registered with the Jamulus central servers, and then a remote person has found it - is all further comms direct?
Is there anywhere I can read about this aspect of Jamulus - the documentation on client and server is extensive and very good, but I can't seem to find much about this part.
I essentially want to know what the bottleneck is for the lists, why it would be a few lists of 150 rather than a single discovery server that can handle millions.
Last edit: Marcos Scriven 2021-02-05
Hi Marcos, I've replied to your question here:
https://github.com/jamulussoftware/jamulus/issues/875#issuecomment-779361853
For anyone else reading in future - have been told the best place to discuss technical aspects is over in Github discussions https://github.com/jamulussoftware/jamulus/discussions
Apparently Github released that functionality back in May 2020, but I only just found out about it.