Re: Ada.Networks.Sockets hierarchy for standardization?

[Michael Erdmann <michael.erdmann@snafu.de>]

Warren W. Gay VE3WWG wrote:
> Michael Erdmann wrote:
> 
>> Warren W. Gay VE3WWG wrote:
>>
>>> For discussion: I have thrown together this evening
>>> a more formalized view of some "chicken scratching" I did on my
>>> train commute home this evening. The diagram is available at my
>>> web site (see PDF link further on).
>>
>>
>> I like it. But may be the names services should be put under
>> Services.
> 
> 
> Hi Michael:
> 
> The problem that I see is that there is a fairly major
> distinction between DNS (Name_Services) and what
> Ada.Network.Services.Internet represents. The later represents
> a database of mappings between numeric port numbers (services)
> and their names (ie. "http" maps to port 80).
>
It makes sense. But i gues these service identifiers may have
to be a little more generalized,  for example as SAPI.


> Name_Services is much more than that. It is an entire protocol
..................
> 
> Maybe an improvement might be to move "Ada.Networks.Services" over
> to child package Ada.Networks.Protocols.Internet.Services
> instead (these would only be Internet specific of course).
I think this is a better idea, since the semantic of what is
a service verry mutch depends on the doain or protocol stack
you are looking at.

> Alternatively, it would be tempting to just merge it right
> into the package Ada.Networks.Protocols.Internet. The mappings
> for ports and the protocol selection constants aren't that
> far apart in concept.
> 
> Other protocols like X.25, may not even need a
> "services" package. 
I do not understand this. You can run FTAM on top of X.25 which
is a service. I gues it would a a good idea to give the term
Service a clear definition which fits into the OSI Model.

Its been years since I used Datapac (X.25),
> but IIRC there is no concept of a port. You just use a DNIC
> (address) and perhaps select the service once you connect to the
> host at the remote end. Perhaps the service selection is
> embedded in the DNIC (I forget). OTOH, the amateur radio
> protocol AX.25, which is based upon X.25, does support up to
> 16 ports (I forget now, but one of these 16 may be reserved).
> 
This is the reason why i think, the better idea is to place
the service identifiers alsways near to the protocol stack/domain
they are refering to.

Michael

>