• From: Robin Berjon <robin@k...>
• To: Haresh Gujarathi <gharesh@v...>, Xml-Dev <xml-dev@l...>
• Date: Fri, 28 Sep 2001 18:08:49 +0200

On Friday 28 September 2001 17:33, Haresh Gujarathi wrote:
> What is more expensive in terms of performance for a Web application?
>
> maintaining DOM in memory for use in subsequent requests or
> recreating the DOM every time a request comes in

It depends on the size of the DOM, on whether you can share it in memory 
accross processes/threads, on how much time it takes to recreate it, etc. If 
it's small and shareable (and preferably read-only) then I'd probably leave 
it in memory. But that's just me.

-- 
_______________________________________________________________________
Robin Berjon <robin@k...> -- CTO
k n o w s c a p e : // venture knowledge agency www.knowscape.com
-----------------------------------------------------------------------
A computer lets you make more mistakes faster than any other 
invention, with the possible exceptions of handguns and Tequila.

• References:
  • What is more expensive persisting DOM in Memory or creatingDOM
    • From: Haresh Gujarathi <gharesh@v...>

• Prev by Date: Re: What is more expensive persisting DOM in Memory orcreating DOM
• Next by Date: Re: %x;? - Opportunity for pedantry and exegesis
• Previous by thread: Re: What is more expensive persisting DOM in Memory orcreating DOM
• Next by thread: support for schemas on ie
• Index(es):
  • Date
  • Thread