is it bad to...

Results 1 to 3 of 3

Thread: is it bad to...

  1. #1
    Join Date
    Dec 1969

    Default is it bad to...

    store a freethreadedxmldom object to an application variable, like so...<BR><BR>set objXML = Server.CreateObject("Microsoft.FreeThreadedXMLDOM" )Set Application("objXML") = objXML<BR><BR>I&#039;m thinking of doing this in the application onstart sub routine.<BR><BR>thnx

  2. #2
    Join Date
    Dec 1969
    Los Angeles, CA

    Default In an application vaiable??


  3. #3
    Join Date
    Dec 1969

    Default I'm with Akhilesh...

    You&#039;d have to do Application.Lock/Unlock around almost any use you made of that object. Which would soon turn into a *huge* bottleneck.<BR><BR>You could probably get away with storing one set of XML in there, but if you used *anything* like "firstChild" or "nextChild" or "nextNode", etc., then you&#039;d have to use the Lock/Unlock, because the object only keeps *ONE* pointer to use for such stuff.<BR><BR>Now as a Session object...<BR><BR>

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts