Nicolas Williams wrote:
> IMO: a truly extensible STREAMS (or whatever) stack would have the
> ability to tag messages with typed-meta-data up (and down) the stack,
> from stream head (and application) to driver, or the reverse, visible to
> all things in between but _without_ having to make any modules aware of
> any such typed-meta-data if they don't need to consume it.
I fail to understand what problem you are trying to solve.
IMHO I see no benefits in a STREAMS beautification project, which is
what "truly extensible" reads like to me ;-)
> E.g., cred_t could be seen as such meta-data if there weren't already a
> field for that in mblk.
db_cred actual highlights the issues around the intended semantics of
any attribute - the current implementation of db_cred is underspecified
leading to potential security issues.
I don't see making it easier to define new extensions as important -
what matters is how carefully we can specify the intended semantics. The
mechanics of adding a new field to some structure is in the noise
compared to the effort to get the semantics correct.
Erik
_______________________________________________
networking-discuss mailing list
[email protected]
