[openbeosnetteam] Re: socket lib...

> > The socket library :
> > - on a call to open it allocates an area of a given size (say 4096
> > bytes)
> > and passes the area_id into the "socket_server" which then just
> > clones it...
>
> Not exactly, there is no need for a socket server - if you mean another
> server as the net_server. There will be the socket library and the
> net_server.

Yeah, the name is more as a concept than anything else. This makes mroe
sense to me if you think of it as provider:consumer or server:client, at
least in my mind.

>
> > Also, this won't be pretty but it's possible. Of course the other way
> > of
> > doing it would be to use a pipe for read/write and just have use the
> > msgs
> > for control functions. In fact that might be better and much faster
> > with
> > less bother about having to have huge buffers hanging around.
>
> Well, what's a pipe? Essentially the same as what we're doing, but I
> don't know if it's implemented (or can be implement) as efficient as we
> can do it - we'd just have to pass area_id's + offsets around for
> memory access, no memcpy()s involved (only in the backend for the BSD
> sockets - or the other way around in the net_server).

If we can make it better then bring it on!  I'll bow to your superior
knowledge on this and await the code that'll be awesome (as normal from
you)!

david

Other related posts: