
|
[openbeosnetteam]
||
[Date Prev]
[02-2002 Date Index]
[Date Next]
||
[Thread Prev]
[02-2002 Thread Index]
[Thread Next]
[openbeosnetteam] Re: Change of heart...
- From: Ksyu & Dima <k2d2@xxxxxxxxxxxxxxx>
- To: openbeosnetteam@xxxxxxxxxxxxx
- Date: Tue, 05 Feb 2002 18:17:59 -0400
Hi everybody,
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).
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).
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.
So, before we decide to implement user-land stack let's consider all
pluses and minuses of such a move.
-Dmitri
David Reid wrote:
> Folks,
>
> I've had some email from people recently about the approach we're taking and
> combined with some other things I'm afraid to say I've changed my mind about
> things.
>
> Don't get me wrong, I still think an kernel land stack will be the way to
> go, but I think it's a long way off and for obos we really should be
> considering the nearer future. Considering the nearer future basically means
> that we look at creating a userland network stack that's compatible with
> beos 5.
>
> While this is a change of course, as we've not really done much so far it
> isn't a big change is it? :)
>
> The change will also lower the entry requirements for everyone and hopefully
> start to provide soem code that people can work on in a familiar environment
> rather than having to jump into a totally new environment at the same time
> as trying to wrestle with the complexities of a network stack.
>
> When we get towards an R2 release (if we ever get there) and we're using the
> newos kernel then we can look at moving over to a kernel based stack, which
> should be much easier having already done the userland code and having a
> bunch of people used to working with network protocols.
>
> I realise this is a change, but think it's one we should make.
>
> david
>
>
>
>
|

|