> >I'm sure it's implied, but could you confirm that this will be fully > >supported for TLI/TPI endpoints? This would provide an elegant fix for > >4300326 and similar bugs in RPC apps. > > > > > > > Yes they are supported.
Cool! > >No strong feeling about the option name, but I would say this: it would be > >great to see such an API become a standard in the future. So you should try > >and make it "standard-ready" from the start - if, for example, the name > >conflict between Solaris and Linux is going to give headaches to the > >standard bodies, use a different name. > > > > > IPV4_PKTINFO/IPV4_RCVPKTINFO should work ? No idea, I'm not a standard body ;-) but IPV4_PKTINFO looks like a safe bet. Nitpicking: I guess you mean IPV4_RECVPKTINFO (with an "E") to stay consistent with IPv6. Blaise _______________________________________________ networking-discuss mailing list [email protected]
