Browse Prior Art Database

Improving Performance of Web Services Via Terse XML Disclosure Number: IPCOM000132576D
Original Publication Date: 2005-Dec-22
Included in the Prior Art Database: 2005-Dec-22
Document File: 2 page(s) / 68K

Publishing Venue



An approach to improving performance of Web Services or reducing storage consumption for large amounts of XML-formatted records.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 61% of the total text.

Page 1 of 2

Improving Performance of Web Services Via Terse XML

Good programming practice calls for verbose XML artifact names. As a result, a tradeoff between readability of XML and bandwidth and CPU utilization exists: - Verbose XML artifact names yield better readability (with all the ensuing positive development and maintenance productivity implications) - but entail

    o higher bandwidth usage during data transmission, and o higher CPU overhead during compression/expansion - Short XML artifact names are detrimental to development and maintenance productivity - but reduce bandwidth usage and CPU overhead - In cases where a large number of XML-formatted records are stored in a database, the database table size may be inflated due to the size of verbose XML artifacts

The solution is intended to ease the described tradeoff, by reducing bandwidth usage and CPU overhead for verbose XML (thus, maintaining development productivity).

1. Translate verbose XML (long names) to an equivalent set of XML artifacts with terse names, in a 1-1 fashion. e.g. (other alternative ways could also be used to derive terse names):

Verbose Terse ------------------------ -----------------------
publicPolicyRequest p0 publicPolicyResponse p1 ..... ..... privatePublicPolicyRequestParameter p197 firstName f0 postalCode p198 insuredValue i0 countryProcessor c0 ..... .....

2. Maintain the verbose/terse translation table along with the XML schema.
3. Web services may provide a method of retrieving the transl...