This is a read-only archive of the Mumble forums.

This website archives and makes accessible historical state. It receives no updates or corrections. It is provided only to keep the information accessible as-is, under their old address.

For up-to-date information please refer to the Mumble website and its linked documentation and other resources. For support please refer to one of our other community/support channels.

Jump to content

Reference of mumble server architecture?


nah4891
 Share

Recommended Posts

Hi.


I need reference paper of mumble server architecture. I have one reference paper ("Mumble protocol 1.2.X reference (WIP)). But I want to get enhanced document of mumble sever. Can I get a updated reference document?


Additionally, Can I get sources of mumble server Windows version?



Thanks.

Link to comment
Share on other sites

Hi.


I need reference paper of mumble server architecture. I have one reference paper ("Mumble protocol 1.2.X reference (WIP)). But I want to get enhanced document of mumble sever. Can I get a updated reference document?


Additionally, Can I get sources of mumble server Windows version?

There's a link on the home page that says "Download source code". Have you tried that one?

The Murmur sources is in 'src/murmur/'


Regarding the "reference paper of mumble server architecture" I believe it's up to you to create that one after you have digested the sources.


GLHF! :)

Link to comment
Share on other sites

  • Administrators

Yup, as fatbob pointed out the source code is freely available.

Alternatively to the source code as a file download you can check out the git repository on sourceforge (webview of murmur folder) or github (webview of /src/murmur).


The server component is named “Murmur” in case you did not know yet.

The server specific code is in/src/murmur.


There is no server architecture documentation, and the protocol documentation is only about the communication protocol.


As a start: The server does not have much logic, it merely redirects packages. It is kept small and efficient to keep resource-usage and latency very low.

Link to comment
Share on other sites

 Share

×
×
  • Create New...