Yeah, instead of making one big mega object that takes lots of messages, there could instead be a suite of objects like one for live capture, one for reading/writing files, one for translating port numbers to services, whatever is appropriate.
.hc
On Oct 1, 2010, at 7:57 PM, Jordi Sala wrote:
Hans, so your proposal is to split the current pdpcap in 2 different objects: one for live (net device) capturing and a second one for pcap file reading?
I like Mathieu's suggested name:1) the Mathieu's reasoning about naming, 2)the objects I think is differentiated of pdp, 3)doesn't lost enterely his original name pd-pcap,
On 1 October 2010 14:20, Mathieu Bouchard
<matju@artengine.ca> wrote:
On Thu, 30 Sep 2010, Jordi Sala wrote:
Yes it can be renamed, I named pdpcap when I started the object (PD+PCAPlib)...,... pcap could be a good name....any suggestions?
Several programming languages use such naming... the hyphen makes it like a namespace in the package-manager, and the complete lack of the "pd-" prefix in the context of pd makes it look like you're loading the original "pcap" itself into Pd (which, of course, makes a lot more sense if that's exactly what your lib does : a plain wrapper and nothing else). I think that this is the kind of naming that users of several other programming languages have come to expect (Perl, Python, Tcl, Ruby, PHP, etc.)
_______________________________________________________________________
| Mathieu Bouchard ------------------------------ Villeray, Montréal, QC
--
Jordi Sala
http://musa.poperbu.net
----------------------------------------------------------------------------
If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of everyone, and the receiver cannot dispossess himself of it. - Thomas Jefferson