On May 17 2013 11:03 AM, andy pugh wrote: > On 17 May 2013 17:51, EBo <e...@sandien.com> wrote: > >> to maybe state it a different way, is a relational database approach >> the best design model? Are there other design (like object >> oriented) >> from which we can leverage utility? > > The tool data needs to be presentable to users in an editor. That is > one constraint that might cause problems. > I also think it is important that there should be no hard-coded keys, > that system integrators can add application-specific data.
both good constraints. I would argue that a couple of hardcoded keys (such as ID, Name/Description), but I agree that extendability is often useful. If user extendability is implemented, will there be guidelines for conventional usage? Is it necessary/useful to log transactions in this context? ------------------------------------------------------------------------------ AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
