[EMAIL PROTECTED] wrote:
> Problem: for developers working against the netinfo framework being
> delivered by the pfhooks project need to be cogniscent of and develop
> against the STREAMS mblk_t data structure. This gives us no flexiblity
> to transition to another data structure and limits us in how we can
> use it.
>
>
> The solution I'd like to start people thinking about is to introduce a
> data type that is presented as a pointer to external entities and for
> which we provide accessor methods.
Can you clarify the proposed scope of your proposal? That is, is it only
netinfo consumers that would use this ADT, or are you proposing something
that would be more widely used?
netinfo would be the first to publish packets in this way.
I'd promote this interface to be used whenever we have something
from within IP wanting to export packets/packet data outside of it
at a programming level.
The intention is that if IP or part of IP changed from using mblk_t's
to something else for moving packets around then the details of
that change would stay inside this API and consumers of it would
be none the wiser.
So I'd encourage others who are exporting packets directly out of IP
to also use this interface, if they were looking to develop a stable
interface.
Darren
_______________________________________________
networking-discuss mailing list
[email protected]
