[openbeosnetteam] Re: Directory Structure...
- From: "David Reid" <dreid@xxxxxxxxxxxx>
- To: <openbeosnetteam@xxxxxxxxxxxxx>
- Date: Fri, 8 Feb 2002 16:24:48 -0000
> > As we want to have all "parts" as modules are we happy with this...
>
> I assume there is a toplevel directory "net"=3F
Well at present we have this...
net_kit/source/server/...
The lib directory contains some C++ code as a wrapper on the server.
> > server/
>
> Perhaps I have missed something, but will we do a network stack in the
> kernel or in user-land now=3F
> And if we are doing it in user-land, is it planned to move it to the
> kernel later=3F If so, we should already try to set up some rules, so
> that this will be easy at a future point.
Yes. I think the main point being if we keep things as modular as they can
be it shouldn't be hard. the abstraction I've added on the mbufs means we
can yank that and add a "kernel level" allocator very easily. generally
keeping things modular should see us able to transition.
However, the big issue remains - how do we talk to the cards???
Doing strings /boot/beos/system/servers/net_server revealed all sorts of
calls, but nothing that jumped out as being the right one. We really need
to get this cracked or we'll be writing drivers as well... :(
david
Other related posts:
