[
Lists Home |
Date Index |
Thread Index
]
Greg, I appreciate the response, and agree whole heartedly that it
varies greatly. To narrow the scope down a bit, which doesn't really
narrow it down much, I work for STAR which does XML Message
specifications for the Automotive Retail industry. The transaction I
was referring to was, retrieving the Data from a database, doing any
type of business logic on the data, populating the appropriate xml file,
validating the file, and then serializing it, and finally sending the
transaction out through a web service (whether SOAP or ebXML).
Now I have tried to explain to the powers that be that there are a wide
number of variables that can affect the overall transaction time, and
XML processing and validation is one of them. Speed in this area is
greatly affected by the size of the xml, the type of validation being
done, and the tools that are being used to create the XML. I'm not
really looking for concrete numbers, but general overall impressions on
XML performance in the above stated life cycle. What percentage of the
time involved does the parsing take. Again, it varies greatly.
The issue has been raised by members as we look at migrating our
standards from OAGIS 8.0 to OAGIS 9.0 which implements Core Components.
I would expect 9.0 to have similiar results as UBL 1.0 since both
implement Core Components and very similar NDRs. Because of the new
NDRs, the size of the XML files has increased, which was to be expected,
and my own ad-hoc tests indicate about 3% increase in parsing and
validation time. Which really in milliseconds is not that huge amount.
Hope that clarifies things a bit. The answers you provided actually
are very helpful.
Dave
|
