Re: [Nagios-devel] XML, JSON, Webservice or something new ?
Posted: Tue Aug 18, 2009 4:13 pm
On Tue, Aug 18, 2009 at 12:31 PM, Sven-G=F6ran Bergh wr=
ote:
> If we think of it as two parts, a filebased DB backend
> and a webservice. Wouldn't it make sense to take a
> look at the DB schema used by Merlin & Ninja, or is it
> too heavy? Possibly the same schema could be used and
> potentially open for the use of Ninja (the officially
> "new" Nagios GUI) without involving Merlin. Don't get
> me wrong here. I really like Merlin, it rocks, but if
> you do not need all its funtionality a lightweight
> DB only alternative whould be nice.
Definitely worth investigating and at the same time I really like the
idea of having an embedded / zero admin DB for Nagios for current
information, one that is not much heavier than the flat files
.
> I realize that some information will be missing, but
> the potential of code re-use is there.
Agreed.
> For the backend my vote is on SQLite. It supports more
> client apps any way.
Good point, tons of language bindings for it as well. need to learn
more about COB.
> I am not the man to judge pros & cons of JSON vs XML.
> But if we are talking web services, the client app
> does not need to be a web page. Is JSON suitable for
> other client apps as well? Just asking, I don't know.
Absolutely, it is lightweight and every language I know of has very
easy to use serialize / deserialize methods that turn JSON into
language specific structures.
- max
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
ote:
> If we think of it as two parts, a filebased DB backend
> and a webservice. Wouldn't it make sense to take a
> look at the DB schema used by Merlin & Ninja, or is it
> too heavy? Possibly the same schema could be used and
> potentially open for the use of Ninja (the officially
> "new" Nagios GUI) without involving Merlin. Don't get
> me wrong here. I really like Merlin, it rocks, but if
> you do not need all its funtionality a lightweight
> DB only alternative whould be nice.
Definitely worth investigating and at the same time I really like the
idea of having an embedded / zero admin DB for Nagios for current
information, one that is not much heavier than the flat files
.> I realize that some information will be missing, but
> the potential of code re-use is there.
Agreed.
> For the backend my vote is on SQLite. It supports more
> client apps any way.
Good point, tons of language bindings for it as well. need to learn
more about COB.
> I am not the man to judge pros & cons of JSON vs XML.
> But if we are talking web services, the client app
> does not need to be a web page. Is JSON suitable for
> other client apps as well? Just asking, I don't know.
Absolutely, it is lightweight and every language I know of has very
easy to use serialize / deserialize methods that turn JSON into
language specific structures.
- max
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]