[openbeosnetteam] Re: Design mess

Philippe Houdoin wrote: 
I would want us to take some time to consider what design we should chose and/or
stick to:

a) put all what's needed for a working stack into kernelland, without user
assistance, for the sake of performance and self-dependency. Put all the rest
in userland libs and regular apps. I included inetd daemon as a regular app.

b) put less as possible (nothing being the best) into kernelland, and make the
network kit looking more like the R5 one, based on a net_server app + its
add-ons + some libs and command line tools.

What do you think? 

- we should not put too much into userland for performance reasons
- do not use net_server whenever possible
- run scripts/apps from kernel-land

Does I overly react?

I don't think so. You thought of an inetd super-daemon and I merely thought of a server for things that should not bloat the kernel too much.

Do you share my worries?

Yes, of course. I don't like having dhcpd, inetd, pppd, etc. running in background, either, and I want the stack to be self-contained.

What's your preferred design?

I could try to make a modified implementation of my ppp_up code because my recent commit makes this part much simpler. I should have thought about this a little bit more. Before those simplifications the implementation was so complex and vulnearable that I wanted to replace it with net_server, but now it can be done in a much better way. Thanks for this mail. :)

Bye,
Waldemar

Other related posts: