Contributors:
Currently, there are serveral things we are planning to develope. These tasks are divided in tasks involving the cliend, tasks involving the server and tasks involving the client shell
Server:
Multinode:
- Load balancing engine in a multinode scenario to avoid situations of having a node with a lot of clients and another one empty.
- Define the management information that the server should send to a client, the client will use this information to balance the load of the server in the nodes of the cluster, it will reconnect to other node if it detects performance problems.
Performance:
The aim of these tasks is to increase the performance of the Serval server
- To distinguish between a data channel and a command channel.
- To avoid mnesia use in the data interchange process because it is time consuming. We have to study
different choices.
- To split the connection_operation and the connection_communications processes in two, one for sending messages and another to receive them.
- To study how to avoid processing the log code when log is not configured.
- To implement a new performance meassure: the host load of a node.
- To search a faster sincronization system database between nodes.
- To study the possibility to define a new architecture with a higher performance.
Authentication.
- To implement new backend authentication systems as, for instance, PAM integration or a module to authenticate with LDAP.
- To introduce role checking for administrative operations.
Security.
- To encrypt UDP connections. At the moment when UDP sockets are used to communicate the client with the server the
Client:
- Windows version of the client.
- To study the posibility of making a new client only written in C. The purpose would be to avoid all the communication problems that are between the both nodes. The shell could be in C too and it would be quite simple of making.
Client shell:
- To let more than one client shell connect at a time to the SERVAL client. Redesign client shell and client erlang node
- Graphic or Web interfaz of the client.
div class="twikiTopicInfo twikiRevInfo twikiGrayText twikiMoved"<&/div>-->
