ri*****@cogsci.ed.ac.uk (Richard Tobin) writes:
In article <87************@gododdin.internal.jasmine.org.uk >,
Simon Brooke <si***@jasmine.org.uk> wrote:real 0m11.328s
user 0m0.020s
sys 0m0.020s
real 0m0.005s
user 0m0.000s
sys 0m0.000s
Presumably the extra time is taken fetching and parsing the DTD.
Fetching, since the cpu time is still only .04 seconds.
Can't you use a catalog to get a local copy instead? Or failing that
an http proxy?
Not reliably, in all the places this software runs. However, it turns
out not to matter very much because in the real application the time
hit occurs only the first time the DTD declaration is seen, and as
this software tends to have uptimes of more than six months a ten
second hit at startup time is not that painful. I'm just glad that I
now understand what's going on!
The only thing that bothers me is what happens if the software doesn't
have access to the public internet at all and consequently can't fetch
the DTD. Presumably it will barf horribly and I'll have to do
something about that.
The easiest thing, of course, would be to not generate the DTD
declaration in the first place, but for purely aesthetic reasons I
don't want to do that!
--
si***@jasmine.org.uk (Simon Brooke)
http://www.jasmine.org.uk/~simon/
;; my other religion is Emacs