hi, I know a core redo is at least months away, but I thought of running some discussions to put some design considerations into the wiki. I've put together a basic diagram of what I think a core redo would consist of, I will edit it based on discussions we have around this. pdf currently at: https://dev.icinga.org/attachments/206/icinga-newcore.pdf
based on previous mails about a design of a core, there are two other open items to discuss, - code convention and standard used - layout of source files for a core redo regarding source layout, I was thinking, - /base/config for all config processing pieces - /base/retention for retention saving pieces - /base/perfdata for perf data pieces etc. open to ideas and discussion. regarding code convention and standard, this is what I have, - tab indenting - closing brace not indented, so that closing brace starts at the same point where the line for the opening brace starts - compile with warnings by default - period runs through valgrind and splint open to discussions -- Hiren Patel [email protected] ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ icinga-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/icinga-devel
