Re: lynx-dev Re: lynx timeline

[Leonid Pauzner]

5-Jun-2003 13:42 Ilya Zakharevich wrote:
> More remarks from Leonid, answered together:

>   A) If the document is in HText cache, the expiration date is ignored.

>       This is not what I observe.  Very often documents get reloaded
>       even with my cache-100-documents settings.

>       Will try to record the URL when I see this the next time...

Try.

>   C) no-cache is equivalent to timeout=now.

>       Do not think so; see time-skew above...

>       Moreover, documents supplying no-cache are "differently
>       broken", so it may make sense to treat them differently than
>       documents with short expiration time.

Yes, it may make sense.  But currently lynx treats "expires<=now is
equivalent to no_cache", and "ignore expires value otherwise".
Try  grep "expires" *.c

>   D) purging on receiving the HEAD is blah blah blah (could not follow
>      it completely).

>       Sorry, what I meant was the "header-part" of the document, one
>       finished by the first "\r\n\r\n" (if I got this correct).

>       When we receive the header, it should be a good indication
>       that the server is going to deliver the document - at least
>       not worse than it did the last time ;-).

Perhaps...

And what if we got "500 Server error" responce, supplied with a nice
"please contact a webmaster" page?
What about non http:// schemes?  Any other ideas?

>       This answers the question about 'z', right?

>   E) We cannot fix major bugs now, when we are close to release.

>       We are still in development branch.  Hurry!!!  ;-)

Do not hurry.
And as we see, the problem is not the implementation details,
but the design decisions. We need an agreement on lynx-dev first.




; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden