[openib-general] [PATCH] osm: trivial fixes for compilation on windows
Sasha Khapyorsky
sashak at voltaire.com
Mon Nov 27 09:33:23 PST 2006
On 18:34 Mon 27 Nov , Michael S. Tsirkin wrote:
> > Quoting r. Sasha Khapyorsky <sashak at voltaire.com>:
> > Subject: Re: [PATCH] osm: trivial fixes for compilation on windows
> >
> > On 14:53 Mon 27 Nov , Michael S. Tsirkin wrote:
> > >
> > > What I always wonder about, is why did opensm invent its own formats
> > > for keeping stuff on disk? Couldn't XML or some other standard be used
> > > for this purpose?
> >
> > Specifically for SA DB file some db format would be better (Berkely DB
> > or so) - this allows to do incremental updates rather than rewrite whole
> > file.
> >
> > But in general it is right question. However I don't have good answer -
> > I don't know any suitable "standard" stuff for this.
> >
> > And XML does not seem to be de-facto globally standard (in some areas
> > it is, so if I will need to think about web interface or so, XML could
> > be good option). OTOH it is harder to read and write than "plain" text
> > file (for me as for user it is not big fun to edit files like
> > /etc/fonts/fonts.conf).
> >
> > Sasha
>
> The point is that inventing your own format means that you have to write your
> own parsers and serializers, and prevents 3-d party tools from integrating
> with you easily.
Right, "yet another parser" is not perfect way, but what is name of the
really better alternative?
I believe most people would prefer to have standard configurations for
their projects and tools, but /etc still introduce new config formats.
IMHO it is generic problem...
Sasha
> I would much rather have a graphical tool do manage the network than edit
> some text files, and to make it possible you should use standard formats.
>
> --
> MST
More information about the general
mailing list