Altova Mailing List Archives>Archive Index >microsoft.public.xml Archive Home >Recent entries >Thread Prev - XMl Dom - update [Thread Next] Re: XMl Dom - updateTo: NULL Date: 9/18/2007 9:52:00 AM
"Steve D" <SteveD@d...> wrote in message
news:5A5845FE-C9B9-431B-900B-B9E152B602E4@m......
> Hi,
>
> I would like to know if it is better (fatser?) to update an xml with many
> line like below?
>
Session("SessionData").selectSingleNode("/zzz[@id='xx']").attributes.getName
dItem("lname").text = xxx
>
Session("SessionData").selectSingleNode("/zzz[@id='xx']").attributes.getName
dItem("fname").text = xxx
> etc...
> or to create a new temp xml create the hole update we need to do an then
> update once the main xml (in this example Session("SessionData")) ?
>
As Martin points out holding an element reference in a variable will be
faster. However if you are not using the FreeThreaded version of the
DOMDocument you may create scalability problems for your app.
--
Anthony Jones - MVP ASP/ASP.NET
| ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
