W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2000

RE: Interesting thought

From: Pravin Goel <pgoel@peoplemoverinc.com>
Date: Tue, 29 Feb 2000 13:17:17 -0800
Message-ID: <77FB1FD98CC4D31183D300C04F1099D303103A@MALONE>
To: "'keshlam@us.ibm.com'" <keshlam@us.ibm.com>
Cc: www-dom@w3.org

the problem is that the browser(at least IE) scans all imported javascript
code for finding syntax errors at the load time. this elongates the load
time unnecessarily. if the code is commented at load time, the page loads so
much faster

-----Original Message-----
From: keshlam@us.ibm.com [mailto:keshlam@us.ibm.com]
Sent: Tuesday, February 29, 2000 12:08 PM
To: Pravin Goel
Cc: www-dom@w3.org
Subject: Re: Interesting thought


> If we could use DOM to uncomment javascript code, it could lead to high
> performance gains at the browser end.

I'm not sure I understand what you mean by "uncomment", and why it'd gain
you any performance.

As far as a DOM view of an HTML page is concerned, your example's all text
nodes. Removing the /**/ is entirely a string-processing operation, at this
level.

You might want to take a look at the Bean Scripting Framework (BSF),
available on www.alphaWorks.ibm.com. That's intended to be a fairly general
approach to invoking scripts on demand, in any of a variety of languages...
and javascript is one of those languages. Of course this requires that the
application recognize the text as a script and pass it to BSF for
evaluation.


______________________________________
Joe Kesselman  / IBM Research
Received on Tuesday, 29 February 2000 16:18:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:13:47 GMT