From: "Christian Molstrom" <cmolstrom@lightsurf.com>
>
> Curt wrote,
>
> > I really don't think you need to bother. The XML part is fairly
> > simple; you have a bunch of attributes with names and values. From
> > this you create objects with getter and setter method. Now come up
> > with some reasonable way of representing the parts of the User-agent
> > header you want to parse, and write a lookup method that takes a
> > User-agent line and returns an appropriate object with the data
> > for that phone. You're now done with the data representation
> > portion.
>
> I am not very familiar with the XML parsers (C++ or Java versions)
> provided by the Apache group (IBM's xml4j and xml4c are based on
> these), but I wonder what performance difference there might be
> between (a) pulling the data straight from xml (probably via SAX)
> and (b) returning data from a getter method in an object.
Which is the fastest approach to getting something working that
doesn't result in something utterly unmaintainable?
If your first guess at that happens to yield an architecture that's
not conveniently optimizable, there's always this step:
rm -R *
But with even a little forethought, it need not come to that.
A very good engineer of my acquaintance said something
that made me hate him for years: "Engineers always like
to optimize their code for something -- speed, space, even
how self-documenting it is. That's all easy compared to
optimizing for getting it done."
-michael turner
leap@gol.com
Received on Tue Feb 26 12:45:23 2002