At 12:57 PM 1/21/2009 -0800, Kevin Doyle wrote:
It's ~both~ how quickly your computer can process the page and how quickly your computer can download the page; however, it's mostly how quickly you can download a page because the processing load of a single web page, no matter how complex, is very, very small. Think of how quickly an HTML page displays when you view it locally versus online.
I guess it just depends on how one defines "rendering" -- to me, that means the process of taking all the parts, performing whatever calculations are needed in order to place them in the correct places (and with whatever effects, etc.), and then putting everything together as a whole. Rendering a graphic in photoshop, or rendering a video file, is basically the same thing, in that sense -- you already have all the parts, it's just putting it together (or applying an effect or whatever) in the correct, specified way -- and thus "downloading" isn't a part of that process.
In fact, this brings me back to my early learning about web design, when we were all taught (as we are still) the importance of specifying image height/width tags and stuff in our code, so that the page (HTML) could *render* itself and display correctly even as the images were still downloading, i.e. two separate processes (downloading and rendering).
But that's me, how I define "rendering", I suppose -- and I guess if others include downloading in that process... well, there you go.
Ron :) Woof?... http://www.Psymon.com Ach, du Leni!... http://www.Riefenstahl.org Hmm... http://www.Imaginary-Friend.ca ______________________________________________________________________ css-discuss [[email protected]] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
