- From: Paul Prescod <papresco@calum.csclub.uwaterloo.ca>
- Date: Fri, 26 Apr 1996 15:58:58 -0400
- To: www-html@w3.org
As I understand it, the main argument for embedding inline code is convenience and performance. Convenience: I think that the important thing to remember is that a URL represents a web "object", not a file. You can _encode_ a URL as multiple files (i.e. server side includes). Or you can use one file to create many URL(i.e. inline CGI). Inline script code can be converted by the server into a _reference_ to another URL (where the server stores the script file). That way the author gets the convenience of "inline coding" and the Web maintains the separation of code from document content (which results in simpler, smaller, cheaper, faster, more stable client software). Anyhow, I tend to think that editing problems should be solved in editing software, not in the interchange language. Performance: On a high-bandwidth line, bringing down scripts and text separately might be faster because it can be done concurrently. On a low-bandwidth line, HTTP persistent connections should make the performance difference between inline and out-of-line quite small. Paul Prescod
Received on Friday, 26 April 1996 15:59:05 UTC