"Also sprach Anson Rinesmith:"
> >Well, as everyone could have guessed, they talk aboout "fields".
>
> > A summary of the RADIUS data format is shown below. The fields
> > are transmitted from left to right.
>
>
> >They then switch to calling them "attributes", for no good reason.
>
> If you were REALLY comprehending the document, then you would have realized
> that fields are used to describe parts of an attribute. This is even under
Thanks, but I know what fields are. Yes, they "are" parts of an
attribute too. Just as cows are animals. But that does not make
animals into cows.
"Fields" are areas of a record. Since attributes are implemented as a
variable type value, that value needs to have space for two things:
1) a type designator ("int", "char", "string253", etc.), that
specifies how the data area should be interpreted
2) a datum.
So you can see that attributes are values that themselves are records
with two fields in them. Nevertheless, they (attributes) are (comprise)
fields in a record - the packet sent in the protocol.
What is the problem? You can have a record with fields that hold complex
values. Those complex values are records with two fields in them - they
hold a real value and a imaginary value, respectively. Nobody is
confused by the idea that a field has fields. That does not make that
field stop being a field!
So what are you shouting about?
My point was only that they started talking about "attributes" without
defining what they meant by the term. I presume they meant "named
field of a record", from what I saw they had been talking about until
then. But perhaps they meant something else. Whatever they meant, they
did not say.
> the description of ATTRIBUTES!
Please - do not mistake your problems for mine!
Peter
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
