lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LYNX-DEV refreshing lynx.


From: root
Subject: Re: LYNX-DEV refreshing lynx.
Date: Tue, 25 Feb 1997 22:14:26 -0500 (EST)

Klaus Weide wrote:
> 
> On Tue, 25 Feb 1997, Mariusz Frydrych wrote:
> > <meta http-equiv="refresh" content="180; URL=/markets/us_markets.html">
> No.  Why should it?
> 
> Lynx gives you a page where, with just one keypress, you can follow that
> redirection yourself, if you want to.  It doesn't allow page authors to
> turn it into a remote-controlled tv with non-standard pesudo-HTTP headers.
> 
I would call being supported by about 85% of the installed base a standard.
But thats just me.  In any case, re-load is a useful tool for authors, and
it should thusly be supported.  (Oh, and the fact that it is a pesudo-HTTP
header is actuly a point in its favior.)

> > I find out that lynx parses the line <meta ... "refresh" ...> because 
> > for a relative URL it gives a message: "Alert!: Refresh URL not absolute"
> > Writting down absolute URL doesn't help.
> 
> It seems you are not just a Lynx user but want to provide Web pages that
> work with Lynx.  Ask yourself whether you really need to used that
> "Refresh" Netscapism at all.  The HTTP protocol (1.0 and 1.1) provides
> *standard* mean for redirection (although without a defined delay
> time), and Lynx of course implements them.  Why not use those?  They
> should be available with every decent HTTP server.
> 

Rederiction differs from client-pull animation in a vital way:  with
client-pull the user can see the first page first.  For a good use of
refresh that you couldn't do with redierection, look at
<http://zero.genx.net/stats.html>. (While your there, join the fun).
   --- James Mastros
>    Klaus
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;

reply via email to

[Prev in Thread] Current Thread [Next in Thread]