On Tue, Sep 04, 2007 at 11:34:55AM -0700, Erik Nordmark wrote: > I don't think the above description is sufficient to figure out what > approach might make sense. There can be many different meanings of > "carried forward" above. A few possibilities are:
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. E.g., cred_t could be seen as such meta-data if there weren't already a field for that in mblk. But might that get expensive? Each bit of meta-data would have to have a type ID that could be used to find a destructor, for example, and probably a copy constructor (for meta-data that needs to be reflected at the head or driver, say). Nico -- _______________________________________________ networking-discuss mailing list [email protected]
