sergio, emil, luis, (chad for dialogic, anyone for licode/lynckya?)
Every time there is a question about media servers, it ends up being a super long thread with multiple cases, with everybody pushing one way or another. Nobody is actually wrong, we just speak about different use case, without knowing. It's also almost impossible to list all the use cases, at least everytime there is a question. I do not think it has to be like that, all the product listed above have something special to them, be it programming language (C, C++. Java, ...) feature, architecture, etc. They simply do not compete, really.
So far my policy had been: provide a high level list, and let the user (who knows his use case better than us), choose, just pointing the questions that should be asked (but not answered) by us. In my e-mail, I did not advocate one way or the other, I just wanted to make sure a choice was not made too early one way or another.
Now, this is not the first thread like this, and I had a thought last time i did not follow up on by lack of time, but i will this time. Do you guys want to write a "as-simple-to-understand-as-possible", "10-questions-to-know-which-type-of-media-server-to-choose" guide? Including real world, reproducible benchmark, with the code for the benchmark put online for everybody to reproduce the results themselves on their side. Whatever the final format (document, blog post at webrtchacks, separate website), if we all were to collaborate in writing the guide, all agreed to his content, I see multiple advances:
- we stop confusing people in e-mail thread on discuss-webrtc leaving there with more question than when he came, and in a state of Fear uncertainty and doubt,
- we don't have to repeat ourselves many time, just to point to the material
- if otherwise perceived as competing members of the same ecosystem reach a consensus on a subject, users can be sure this is the right answer, and we can move forward tackling other problems.
Note that Temasys does not sell a media server, even though we have that capacity in our platform. We are kind of neutral here.
I'm happy to put my money where my mouth is and not only to start the first draft from a buyer point of view, and to provide the base for a common benchmarking test suite.
What do you think?