Microsoft Knowledge Base Email Alertz

(252675) - When you send information between component tiers in Extensible Markup Language (XML), you may want to use strings rather than instances of the MSXML DOMDocument object.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 252675 - Last Review: September 30, 2003 - Revision: 2.5

INFO: Use String Parameters to Handle XML Documents Across Tiers

This article was previously published under Q252675

SUMMARY

When you send information between component tiers in Extensible Markup Language (XML), you may want to use strings rather than instances of the MSXML DOMDocument object.

MORE INFORMATION

When you pass information between tiers, there are several advantages to using strings:
  • Your components can be called from (or consumed by) clients that do not have access to the XML DOM objects.
  • XML Documents are not "marshalled by value." If you return an XML document, the instance lives on the server. Each call to a property or method on the XML DOM object must go across the network to the original server. By using strings, you reduce network traffic significantly, and you decouple client and server failures.
  • The internal XML implementation of both client and server can change independently; for instance, if you choose to use another XML parser, or if you obtain XML from another source such as Microsoft ActiveX Data Objects (ADO).
There are, of course, exceptions where other mechanisms may prove more appropriate, such as when:
  • none of the above considerations is relevant to your situation.
  • the components that are passing DOM references are very cohesive, and will remain tightly bound both logically (shared development cycle, shared usage modes) and physically (same computer, same process) for the foreseeable future.
  • the documents are large and complex, and reloading and reparsing would be expensive, or would occupy resources for too long (reparsing a complex document while within a transaction may not be convenient).

REFERENCES

MSDN XML Developer Center:http://msdn.microsoft.com/en-us/xml/default.aspx (http://msdn.microsoft.com/en-us/xml/default.aspx)

W3C XML Reference: http://www.w3.org/XML/ (http://www.w3.org/XML/)

APPLIES TO
  • Microsoft XML Parser 2.5
  • Microsoft XML Parser 3.0
  • Microsoft XML Parser 3.0 Service Pack 1
  • Microsoft XML Core Services 4.0
Keywords: 
kbdcom kbguidelines kbinfo KB252675
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate