FreeLists / openbeosnetteam / [openbeosnetteam] Re: libbind.so status

["Philippe Houdoin" <philippe.houdoin@xxxxxxx>]

> libbind.so compiles fine and there are not linker errors when I run 
> Mozilla.
> But it does not resolve the hostname. :(

A bad point when resolving hostname is what libbind.so is expected to 
do at most :-)

> All functions are called, but select() always times out.

Maybe an issue with our select() or BONE select() implementation?
 
> Shall I commit the source so you can have a look at it, too? It would 
> be a 1.2MB commit, 

Damn, too late, I just saw the CVS notifications, I should have react 
earlier.
My reaction would have been: "What? 1.2MB!?!"

You've port the whole BIND library I guess, but we really only need the 
client part.
Why not only port/update the client part we do have ported already in 
src/kits/network/libnet/* ?

> Unfortunately, I could not leave all headers and sources untouched. 
> The *_r functions want _REENTRANT to be defined, so I added
> #define _REENTRANT 1
> to netdb.h and resolv.h. Also, our private pthread code has some 
> issues that need special handling. All changes are documented in 
DEVNOTES.

I'm worried you put ISC headers in public/posix tree instead of private
/net/isc or even under src/kits/network/libbind/headers where it have 
make more sense. Most if not all ISC headers are in no way POSIX ones 
but, well, just BIND headers. Sound kind of private to libbind to me...

For POSIX standard headers list, check here:
http://www.opengroup.org/onlinepubs/007904975/toc.htm

Oh, BTW, you're right, we need pthread support for better POSIX 
compliance, even if I always thought being 100% POSIX 1003.1 compliant 
for R1 is not our goal. (I never know pthread.h was made an official 
POSIX API!)

I may not being best placed to debate about code as I recently dropped 
out of OBOS top 10 contributors list ;-), but, well, here my point:
I don't know how you guys feel about our code and headers volume, but I 
start to feel some bloatness and mess as we more and more *port* UNIX 
stuff. 
I'm not saying here we should code our own DNS & co support ourselves, 
clearly porting BIND client was and still is the way to go. 
But it's maybe not always the case... and often the port *cost* is 
important: more headers, more tweak to make it compatible, more tricks 
hard to understand for future OBOS coders, etc.

To put shortly, I concerned about the UNIXification of OBOS code.
BeOS was not an UNIX, and I always like the cleaness feeling you get 
browsing develop/headers/*.
I think it's important for the project to keep control on our public 
headers to keep this BeOS *feature* that way.

The net kit is more exposed to such issues due to de-facto UNIX origin 
of most INET network stuffs...

So, let's toss blindly all these headers under private/* subtree!
Just kidding :-p
But I think we should decide some policy on that topic.

What's your opinion, guys?

- Philippe

--
Fortune Cookie Says:

i'm living so far beyond my income that we may almost be said to be
living apart.
                -- e. e. cummings