Re: SSI

by "Harold A. Driscoll" <harold(at)driscoll.chi.il.us>

 Date:  Fri, 17 Mar 2000 20:51:01 -0600
 To:  "Kehvan M. Zydhek" <kehvan(at)zydhek.net>
 Cc:  "tim booker" <timbooker(at)lineone.net>, "Hwg Techniques \(E-mail\)" <hwg-techniques(at)hwg.org>
 References:  mallard
  todo: View Thread, Original
At 20:22 17-03-00 , Kehvan M. Zydhek wrote:
>As in your earlier reply regarding the ampersand character 
>in the email name, you spend a lot of time quoting the specs 
>without giving links to the spec 

Excuse me, but I must confess that I didn't realize that there were list
participants so clueless as to neither know where any of the many IETF RFC
archives are located _nor_ to look at the Guild or W3C Web sites that
contain such information.

The IETF RFC documents can be found at http://www.ietf.org (for example RFC
822 is at http://www.ietf.org/rfc/rfc0822.txt).

>or suggesting alternatives to alleviate the problem or 
>answer the question. 

Perhaps then you might benefit from reading my reply more carefully. The
answer is very simple, write correct HTML when referencing the email
address in question, properly quoting the & as &amp;.

>Additionally, even though Windows98 was built from 
>what was a 16-bit operating system, rest assured that 
>it is, in fact, a 32-bit operating system. 

Actually, it depends on what you choose to read. If you read the technical
information, you'll see that it in fact runs much of its critical code
(such as device drivers and even the command processor) in 16-bit code,
performing frequent micro-processor mode shift between 16-bit and 32-bit
modes.

The nature of the Intel 80x88 chip design is that it can run in native
32-bit mode, or it can run in 16-bit mode, switching to and from 32-bit
mode. The latter sacrifices substantially in performance, security, and
robustness.

Marketing fluff, ignoring the ugliness under the hood, can claim that much
of the application-layer code (and some of the system code) is 32-bit. But,
as anybody who has tried to diagnose application crashes finds that many of
them are actually flaws in device drivers (typically but not exclusively
video drivers). Were it a true 32-bit system, such would not need to be the
case.


>In answer to your question regarding the format of 
>LAST_MODIFIED in an SSI, I paraphrase from "Teach 
>Yourself CGI Programming with PERL 5 in a Week" 2nd
>Edition by Eric Herrmann, published by sams.net, pg 81-84:

This answer is likely correct for some SSI implementations, but SSI is a
server-specific extension... nothing is standardized.

Safe computing,  /Harold
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Harold A. Driscoll                 mailto:Harold(at)Driscoll.Chi.IL.US
#include <std/disclaimer>                 http://Driscoll.Chi.IL.US

HWG hwg-techniques mailing list archives, maintained by Webmasters @ IWA

This page is part of a preserved archive of archives.hwg.org. The site is no longer active and its content is not maintained. For enquiries about this archive, write to archive(at)iwanet.org.