> On 4.4.2012 13:57, Jiri Svoboda wrote: > > I really don't want to discourage you, just warn you that the > > networking stack is still not in such good shape as you might be > > thinking. I suggest it might be better if you either come up with > > another idea or at least modify your proposal in such way to be less > > dependent on networking. I would not want to end up in a situation > > where you could not progress because I haven't finished some part of > > the network stack just yet :-( After all, I am working on in in my > > spare time - and this is very scarce sometimes. > > I would not be that much against a project like this (with preferences > towards SSH). Sure, such a project would be very much a bleeding edge > one thanks to the bleeding edge networking stack (both versions), but on > the other hand, the TCP part is already rewritten and it can handle > normal traffic. The proposal could be modified so that whenever there > occurs a roadblock in the form of a buggy networking stack, the proposal > would redirect the student to help debug and fix the problem. From this > point of view, it would make sense to work with the new stack only. How > about that? I am not so much worried that it cannot be done now rather than that it will be a waste of effort.
The problem is that SSL/TLS sits somewhere between the transport layer and the application interface, i.e. somewhere around the sockets implementation - and that's an area which is still pending rewrite. SSH is little better, because it sits on the application layer (i.e. on top of sockets API) which will be retained at minimum for compatibility purposes in libposix. In the first case there is certainty of work being wasted, because later SSL would have to be modified (perhaps very heavily) as the transport layer interface changes. For SSH you might get away with less change by sticking to the sockets API, but if wie actually do introduce our own API for networking, that would mean our native SSH implementation would use a compatibility API instead of a native one .. yuck... or you would have to rewrite it yet again... -Jiri _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/cgi-bin/listinfo/helenos-devel
