
|
[openbeosnetteam]
||
[Date Prev]
[01-2002 Date Index]
[Date Next]
||
[Thread Prev]
[01-2002 Thread Index]
[Thread Next]
[openbeosnetteam] Re: Life?
- From: Erik Reid <reide@xxxxxxxxxxx>
- To: openbeosnetteam@xxxxxxxxxxxxx
- Date: Tue, 15 Jan 2002 06:30:38 -0700
Quoth "Jean Schwerer":
>
>Hi all,
>
>[ A happy man has recovered all of the data on its lost partition :-) ]
Yay! :)
>[Emmanuel & Erik]
>>> I've got a compiling library skeleton, no net_server skeleton yet. Should
>>> I commit this?
>>
>>Of course !
>>Let's talk about it here :-)
>
>Didn't check at this time but if you haven't done so yet please let me tell
>you your co
m
>mit is
>pretty much expected, hoped and awaited for :-).
Well, I hope not too anxiously, given that there's no real code. :P
How are the headers being handled? I just checked the mediakit ones, and
they've
got "Copyright 1997-98, Be Incorporated, All Rights Reserved" all through them
still..
This doesn't seem like a good idea. Ideas?
I'll throw in all the stuff except the headers, I think it compiles right now if
one were to compile in a BeOS environment.
>[Erik]
>>Are you working on the network stack itself?
>>Where are you with what you've got?
>
>Yup. I'm working from nettle source. I'm close to nowhere cause I had close to
>no time at all to spend on it. But I should find some time for it soon.
nettle source? (Sorry, I'm not much of a BeOS person, more interested in
coding/learning about network stuff than specifically in the OS)
>Emmanuel said he hadn't much time but he's still willing to put together
>documentation on what he found out about interfacing with drivers.
Cool. How close are we going to stay here? Given that we have influence into
the kernel and obviously the netserver, are we going to aim for driver
compatibility,
or just do our own interface in the end? (I haven't looked at the driver
interface
much, so I don't know if it's good or bad, just wondering)
>On a different note, you might have noticed than John Gabriele posted (on the
>main OBOS list) a question about how the BeOS Network Kit compares to an API
>called ACE. I don't know ACE at >all and just gave a very quick and fast glance
>at their website. Judging from the 30 seconds I spent there it looks to me ACE
>might be some kind of MUSCLE equivalent.
I think ACE is a much higher level API than what we want in the netkit.. I
don't
know much about it, just remember it being rather large and annoying to compile
for the most part. :)
|

|