Re^2: Design opinion, configuration inheritance

[naChoZ]

> My first impression is that your entire
> developer team is mis-using OO. Nagios
> doesn't have classes - it has parameters.
> There are no behaviors associated with
> that data, other than getters and
> setters. So, maybe you should have a
> single class that actually composes the
> data structure (presumably a hash) from
> other data structures.

I'm greatly simplifying what it's all about. There's actually quite a bit more to it. It's more of an API, really.

They have their own homegrown set of web apps here that all use the same basic framework and I'm building the asset manager/nagios interface into that. I've modeled it a little bit like RT.

I'm not entirely certain how you define 'behaviors' in this context, but it's definitely more than just getters and setters.