[Serval-devel] Report

[Miriam P. V. <mir...@gm...>]

Hi j.

I may do the paper you are requesting but i think it is not worth to do
it because enough information is actually avaliable in the web

The first point is about the current architecture of serval. As you know
Serval's architecture has not changed since my incorporation to the
project in July. I only focused on performance and fault tolerance
issues. There is a huge amount of detailed information in the
development web, the report Javi made in september and the report I gave
to the University.

The second point is the description of the performance limitations with
examples.  That one is exactly what I am already describing in the
sheduled web of Serval. I am currently analyzing the source code, and I
have found some mistakes. I'm writing them down in my own notes and some
of them have already been reported in the web. The reports have a huge
amount of information explaining in detail what i think is wrong with
the current implementation and some possible solutions. There are also
some examples of the problems and their solutions. I'm working on it
daily. 

The third point you mention is describing a new architecture and I think
it is too soon to focus on that. First I need to research deeply into
the bottlenecks of the client and the server. Designing this
architecture could take me at least one more month, and as it is extreme
programing, I mustn't do it at once. The proper way would be to focus on
little problems, modify them and try to know if the solution is more
efficient. Anyway I want a deeply vision before touching the code.

The fourth point is connected with the second point and is already been
written in the web.

Up to know is for sure we'll be making severe changes into the client.
	- C part will almost dissapear. There will only be erlang node and C
part will be linked in erlang. It will have only functions for tapup ,
reading and writing. 
	- Two ports, data and control.
		- data only udp connections. (some encrypted)
		- control i dont care.
	- 2 erlang processes for each port.reading and writting.
	- Server part will have a process for each vlan with the list of
clients. Syncronization engines. (Observer pattern).
	(... )
		
As you know, I was sending e-mails with the changes information. As I
couldnt receive any mail from this list I gave up sending them and
continue writting in the web. Anyway, any doubt please report. 

Everybody is invited to check the web. 

Cheers.