VOEvent working draft published: version, param
Tony Linde
Tony.Linde at leicester.ac.uk
Sat Jun 25 04:28:33 PDT 2005
> That depends on whether you're using a SAX or DOM based
> parser, surely?
Beyond me - do you mean the SAX one would be significantly slower because
you've got to fire up the string lookup / UCD checking / etc process each
time you hit a <param> element instead of getting them all and processing
them all in one hit?
I still reckon it'd be slower using any method to do the string... approach
than the namespaced element one.
T.
> -----Original Message-----
> From: Alasdair Allan [mailto:aa at astro.ex.ac.uk]
> Sent: 25 June 2005 12:10
> To: Tony Linde
> Cc: 'IVOA VOEvent List'
> Subject: RE: VOEvent working draft published: version, param
>
>
> > Now this is the bit of your argument I don't get, Al. are
> you really
> > saying that it takes less time to act upon:
> > <param name="ActionItem" value="HoistTheMainsail"
> ucd="ship.sail.action"
> > />
> > than:
> > <shipns:ActionItem>
> > HoistTheMainsail
> > </shipns:ActionItem>
> > or, if you want to keep the weak typing:
> > <shipns:ActionItem value="HoistTheMainsail" /> ?
> >
> > Sorry, I don't buy that. In the case of the <param> you
> need to find
> > all the <param> elements during the record parsing, match the names
> > against your internal lookup table of names you understand and then
> > act upon them, while with the simple element inclusion the
> action is
> > fired when the record parsing hits the recognised element.
> The latter
> > has to be significantly faster.
>
> That depends on whether you're using a SAX or DOM based
> parser, surely?
>
> Al.
>
>
More information about the voevent
mailing list