[openbeosnetteam] Re: Protocols types

"Waldemar Kornewald" <Waldemar.Kornewald@xxxxxx> wrote:
> How are the protocol types managed? The ethernet module has them hard
> -coded.
> Do you think this is a good idea? It is not a big problem to hard-
> code them
> into each module because we maintain and extend the code anyway, but
> wouldn't it be better to make a driver configuration file that is 
> loaded by
> the core module?
> It could look like that:
> 
> "ethernet" {
>     "IP"=0x0800
>     "ARP"=0x0806
>     "RARP"=0x8035
> }
> ...

I don't like hard coded (in the wrong modules), but I dislike 
configuration files even more.
The stack should scan through the available modules (even on request 
when a new one is added at runtime, could be done with node monitoring 
in the new kernel), and should ask them what services they provide.
I don't think it's very user-friendly when you first have to config 
something that obvious and all files are already in place anyway. So, 
if we can avoid such a config file, we should do it, IMO.

Adios...
   Axel.

Other related posts: