Hello, Ive recently integrated the PF_RING ZC library in my network flow generation software.
First of all, I wanted to say that it works great and we are getting fantastic performance. Im new to the mailing list, so I apologize if this was brought up in a previous post but I wanted to bring to your attention the issue with incompatible API changes from 6.0.1 to 6.0.2. I recently upgraded to PF_RING ZC 6.0.2 (from 6.0.1) and was surprised that my software does not even compile with the new version. These changes were not listed in the Changelog and the API documentation still reflects the 6.0.1 API: http://www.ntop.org/pfring_api/pfring__zc_8h.html The largest and most incompatible change that I have found is the change to the pfring_zc_pkt_buff data structure. The pointer to the packet data is no longer available through this structure and is only available through an additional function call that required me to search the header file to find. In my opinion, a change like this should require a major version number bump to notify developers that the API has changed significantly. Going forward, I am wondering if I should expect incompatible API changes in minor patch releases or do you expect the API to stay somewhat stable? Additionally, it would be nice if there was a way to get the version of the library so the software that uses it can determine compatibility with a particular version through Autotools (possibly shared object numbers) . Thank you and best regards, Emily _______________________________________________ Ntop-misc mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop-misc
