FreeLists / openbeosnetteam / [openbeosnetteam] kernel- or user-land [Was: Change of heart...]

[<j-schwerer@xxxxxxx>]

Hi,

>what worries me about such a change that in the future (when the stack =

>moves into the kernel) we will have to rewrite a lot of stuff (I am =

>afraid that even if the plugin approach is taken the code will not be =

>iimediately reusable).

As I put it in an earlier mail I don't clearly understand how much of a
difference that brings on a network stack (in which I would expect most o=
f the
code to be protocol-related and "anywhere-land" independant?). Therefore =
Id'
really appreciate if someone would *clearly* (clearly, as in "clearly det=
ailed
with examples for the dummies" =3DP) explain WHY there would be "a lot of=
 stuff"
to rewrite.

>At this point it doesn't really matter whether one should learn kernel =

>API or learn how to write network server plug-ins (IMHO the difference =

>will not be that big).

IMHO I also think there shouldn't be that big a difference. So I am getti=
ng
even more confused now when you say there would be a lot to rewrite ^_^

>With the approach that was discussed before (plug-in architecture) the =

>"entry requirements" depend not as much on ones understanding of =

>kernel structures and API, but rather on understanding of networking =

>protocols and algorithms to implement them, which will be the same in =

>either case.

Jean


____________________________________________________________________
Get free e-mail and a permanent address at http://www.amexmail.com/?A=3D1=