On 02/25/2009 04:46:46 PM, Paolo Lucente wrote: > All this said, let me just shoot a proposal: as the in-memory table > client/server communication is already based on request/reply headers, > operation codes, etc. (so let's say the protocol is there) what about > keeping it simple by encoding all of this in either UDP or TCP packets > with a bit of socket programming?
Bah. All the time I'm spending messing around in shell makes me think I'd be better off extending pmacct. I guess my reluctance is that if you don't like it all the work would be wasted. We would really have to agree on an approach. Naturally you could still reject whatever code I write if you think it's broken or ugly. What do you think of the ideas so far? (I do need to get something working quickly.) Karl <[email protected]> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
