Thanks for the quick reply. On 02/28/2009 09:47:59 AM, Paolo Lucente wrote:
> * the socket approach would be, IHMO, the best but requires more work. > This > might be done in alternative or in addition to listening on a UNIX > socket. > The way in which it should be coded is similar; as operations in the > IMT > plugin are very quick (and to avoid concurrency overhead) i would > advice > something that serves only one client per time; it currently works > this way > for the UNIX socket. The reward is that once the connection is > served, the > existing code on both the client and the server can be fully > re-used. > Optionally, multi-threading can be introduced: a small but useful > thread > pool management library is already existing inside the pmacct > package and > is written by Francois Deppierraz. What do you think about re-creating the server's sockets on the client and then just using the regular pmacct on the client? This would mean having another daemon on the client that would feed data over the network to the client sockets. On the server side this would be taken care of by pmacctd itself. > One more thing: what about authentication? With an UNIX socket this > is > easily > solved by the underlying filesystem. Anything network-based, should > require > you to take care about it (once again, can't speak for how it's going > to work > for the socat approach). I have no plans for any sort of security. (I plan to use a separate physically secure network.) I see nothing that would preclude adding in any sort of security once the basics are in place. Would the lack of any sort of security prevent you from merging the code? I also have a licensing question. You have pmacct licensed under the GPL v2 only. If I write an entirely new program (e.g., the daemon that runs on the client box) I would prefer GPL v3 or later. Naturally any code I submit for inclusion into your existing programs I will submit under the license of your choice. Thoughts? Karl <[email protected]> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein P.S. Did you notice the 2 strcpy related patches I sent to the list? I don't want them to get lost. _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
