> Anthony (I think): It does not work for my on *any* browser I have.
> It does not work on: ... 6 browsers.
> None of them will let me view the pages.
> That's what's so bad with it!
Adrian: Which 6 browsers are you using? and why?
Adrian: I'm yet to see a problem with this web site. What *exactly* is
going wrong for you Anthony? What error messages are you getting? What is
it doing when it doesn't display the pages? Do you get any part of the
pages? Which part? We had this conversation about the FC Log not so long
ago, if you just tell us it's wrong we can't fix it.
> Alain: On a societal-level, I will hazard the
> prediction that an enormous backlash against the Web
> is brewing in the near future. Instead of moving
> forward with CSS, XML and client-side scripting (JS or
> VB), we are heading in the opposite direction, towards
> removing features like frames, tables, images ... and
> the widespread popularity of Linux and all of that
> other command-line stuff ... we are regressing in
> terms of user-friendliness.
Adrian: Actually, Linux is really pushing to become more user friendly. It
is increasingly becoming graphical instead of command line based and is
coming up with a number of novel ideas which make life easier. Also
remember that MacOS X is based on a BSD kernel which is a UNIX system. I
think the same thing is happening with the web - it appears to be forgetting
user friendliness but it isn't really. For instance, images and tables make
the page load slower, frames can make it more difficult for screen readers
and the blind. Client-side scripting is struggling because of (often
unfounded) security concerns. It will pull through though. We have to
improve net speed first as that is the most user unfriendly part right now.
>> Anthony: My only guess is that Alain's CGI
>> is spitting out f-ed up headers, which are
>> being eaten alive by my ISP's webcache.
>
> Alain: The HTTP-protocol portion of the transaction is
> automatically taken care of by WebStar 2.1, and always
> has been. My CGIs only generate the HTML portion (HEAD
> and BODY).
Adrian: You will need a Content/Type header to be returned by the CGI
though. I just forget exactly what it is - I'll look it up if Anthony
doesn't post it for me. :) This may be causing a few problems with really
stupid browsers and/or ISPs but anything half decent can handle not having
this header.
Adrian Sutton
**************************************************************
Email: [EMAIL PROTECTED] Ph: 3714 4649
We have nine children now � half boys and half girls.
-- Mark Twain.
**************************************************************
