Tom, I've roughed in more or less the approach I was thinking about for an attribute registration system. One thing that remains unclear to me is whether this system is intended to operation per-application (as I have designed my proposed API) or it is intended to be global along the lines of the "standard" attributes. Generally speaking we try to avoid hard-coding assumptions about that sort of thing into the libraries - the "standard" attributes are the way they are primarily due to legacy design decisions - but if the idea is to have a registry of user defined attributes that is universal I'm not sure how that could be (or even whether it should be) addressed at the library level. Do you happen to have a pointer to previous discussions with Sean that might help clear up the long term design goals?
Thanks, Cliff ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
