What are you performance requirements? e.g. how many transactions per second do you expect? What amounts of data are you communicating? What's involved in the XSL; is it a simple transform, or are you expecting to use alot of XPath or XQuery?
Creating XML, transferring XML, parsing XML, running the XML through XSLT, then parsing the transformed data is not as quick as other methods, for sure. But, if fits your performance requirements, it's a trade off between performance and flexibility/maintainability. On Thu, 29 Jun 2006 11:23:21 +0000, Paul Cowan <[EMAIL PROTECTED]> wrote: >Hi all,I am working on a web app where we are communicating with Navision, the way it works is that we send and receive xml messages.Now I'm thinking of using serialisation to render my objects into xml and then perform an xsl transform to render it in the required xml and for return values I am thinking of performing another xsl transformation to enable me to deserialise the return type back into my domain objects.My only concern with this approach is performance. I am using .NET 2.0. Does anyone see this as being a potential performance killer? Are there any ways of performing these xsl transformations quicker? =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
