From: Alan <alan@ctrl-alt-del.com>
Date: Tue, 19 Aug 1997 05:34:20 +0800
To: Ray Arachelian <sunder@brainlink.com>
Subject: Re: New use for  Eternity Server
In-Reply-To: <Pine.SUN.3.96.970818165835.24071H-100000@beast.brainlink.com>
Message-ID: <Pine.LNX.3.95.970818140727.20920I-100000@www.ctrl-alt-del.com>
MIME-Version: 1.0
Content-Type: text/plain



On Mon, 18 Aug 1997, Ray Arachelian wrote:

> On Mon, 18 Aug 1997, Alan wrote:
> 
> > Uh, not exactly...
> > 
> > The web browser will not show the code correctly.  (It will have problems
> > with > and <, for example.)  I guess it depends if you want it for display
> > or for execution.
> 
> I've never had a problem (using Netscape) just simply opening up .c
> files directly.  It recognizes it's not HTML and display's the < and > (as
> in #include <blah.h> fine.

This is because it is defaulting to text/plain for the mime-type.  

> However, you're right about the <PRE> tags, using them won't work. :)  Not
> using them works better... though having a filter will do the trick I
> guess...  Mispoke before.... the #includes show up without the <header.h>
> info...

If you think that is bad, try using segments of Perl code between <pre>
and/or code tags...  Mangle does not quite describe it well enough.

> > Maybe the eternity documents need to have some sort of content header.
> 
> Or better yet, just compress the damn things with GZIP or ZIP, or
> whatever, and have the servers handle them as binaries.  Would work better
> in the long run anyway since it will waste less space.

This assumes that the user has support for those compression formats.  (I
run into this too much with Solaris and Windows, for various reasons.)

> Can current eternity servers handle plain binaries?

And if they do, what encoding format do they support?  (Mime, Base-64,
and/or uuencode.)

alan@ctrl-alt-del.com | Note to AOL users: for a quick shortcut to reply
Alan Olsen            | to my mail, just hit the ctrl, alt and del keys.