FreeLists / openbeosnetteam / [openbeosnetteam] Re: PPP API

["Nathan Whitehorn" <nathan.whitehorn@xxxxxxxxxxx>]

> > Hi,
> > I just had some time and completed the draft PPP kernel API. There 
> > is only
> > one comment, but the source should be understandable. It is mostly 
> > for the
> > add-ons.
> > All objects have a "K" prefix so that the names do not collide with 
> > the
> > later userland API.
> >
> > You can download it here. Comments are welcome, of course.
> > http://zeus.mpg.goe.net/~tuvok/obosppp/kpppapi.zip
> 
> These overwhelming responses tell me that: either my design total ***
> * or it
> is boring or nobody is here or maybe you are not interested. :)
> This is only a small draft and it will change a little bit. I am not 
> very
> sure about the K prefix. I could be enough to add it to the header. 
> There
> are some classes missing. The encapsulators will become a new class. 
> Should
> I use the OpenTracker style? It looks so ugly. :) I like the BeOS 
> style
> (look at Application.h).
> Should I continue? Nathan?
> I will just code on...

I've been busy lately, so I haven't had to time to look at it. However, 
as my response has been requested, I feel obliged to at least say 
something. Perhaps I can remedy the situation by dumping lots of code 
at you guys: http://members.verizon.net/~vze236yf/net_server_stuff.zip 
This code was written in another context, and (for a variety of 
reasons) is probably slow as hell, but it does illustrate some of the 
ideas I've mentioned. It also (as far as it goes -- which is a generic 
ethernet driver and a PPPoE stack) actually works, and does so quite 
well. I have omitted all of the support libraries, however. If you want 
them, e-mail me. Maybe that will delay you long enough for me to be 
able to take a look at yours.
-Nathan

--
Fortune Cookie Says:

After the last of 16 mounting screws has been removed from an access
cover, it will be discovered that the wrong access cover has been
removed.