Currently, the server-client communication is based on text messages separated by tab (e.g starttrack \t trackname...), processed by one big if statement across multiple methods. It is a mess and sadly totally unmaintanable since we cannot read most of it and do not understand how it works at all.
I would like to start designing a new proper protocol which would include all of the messages that are currently processed and that would allow extending it to for example enable user roles or even check version.
To do that I think we should have a separate branch because this is an effort that will take a long time a lot of work.
WDYT @PhilippvK ?
Currently, the server-client communication is based on text messages separated by tab (e.g
starttrack \t trackname...), processed by one big if statement across multiple methods. It is a mess and sadly totally unmaintanable since we cannot read most of it and do not understand how it works at all.I would like to start designing a new proper protocol which would include all of the messages that are currently processed and that would allow extending it to for example enable user roles or even check version.
To do that I think we should have a separate branch because this is an effort that will take a long time a lot of work.
WDYT @PhilippvK ?