175107Sfenner TODO list for libpcap 275107Sfenner======================= 375107Sfenner 475107SfennerImportant stuff (to be done before the next release) 575107Sfenner--------------- 675107Sfenner 775107SfennerGeneral 875107Sfenner 9214518Srpaulo- configure should not be in Git. Most open source projects have an 1075107Sfenner autogen.sh script to run autoconf etc. after checkout. I think we 1175107Sfenner should stick to the standard. 1275107Sfenner 1375107Sfenner- The source files should be better documented. There is no official 1498530Sfenner design guideline for what is done where. There should be a common coding 1598530Sfenner style (okay, you can guess that by looking at the code) and a guide for 1675107Sfenner what needs to be documented. 1775107Sfenner 1875107SfennerLess urgent items 1975107Sfenner----------------- 2075107Sfenner 2175107Sfenner- Better documentation and cleanup of the interface. I am seeing a few 2275107Sfenner problems at the first glance which needs fixing: 2375107Sfenner + pcap_lookupnet makes little to no sense with protocols != IPv4 2498530Sfenner + not very well suited for interactive programs (think ethereal). There 2598530Sfenner should be a way for the application to get a file descriptor which it 2698530Sfenner has to monitor and a callback in pcap which has to be called on 2798530Sfenner activity (XXX - "pcap_fileno()" handles the first part, although 2898530Sfenner "select()" and "poll()" don't work on BPF devices on most BSDs, and 2998530Sfenner you can call "pcap_dispatch()" as the dispatch routine after putting 3098530Sfenner the descriptor into non-blocking mode) 3175107Sfenner + too many functions. There are a lot of functions for everything which 3275107Sfenner violates the KISS principle. Why do we need pcap_strerror, pcap_perror 3375107Sfenner and pcap_geterr? 3475107Sfenner + the manpage has a brief description of each function but where is the 3575107Sfenner big picture? Seems like you need to buy UNP for that... 36