> 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!
Alain: Beggars can't be choosers, my folks always told
me. I spent 10 full days adapting a system I have been
developing for 2 years now, and filling it up with the
content that I could cull from our mail archive and
contributions. I foolishly assumed that a preliminary
version that runs on recent versions of Netscape and
Explorer would be sufficient for our short-term needs,
e.g. to kickstart our collaboration.
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.
> 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).
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
