[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev Year 2000 Compliancy
From: |
Larry W. Virden |
Subject: |
Re: lynx-dev Year 2000 Compliancy |
Date: |
Fri, 4 Dec 1998 06:05:37 -0500 (EST) |
From: David Woolley <address@hidden>
> Most probable reason: he's received a management directive to confirm it
> for all the software, and the easiest way is to pass the responsibility up
> the chain by asking the supplier.
While in the case of lynx he has the source code, in other cases he would
have no other alternative than to go to the supplier. Rather than every
lynx user going thru all the source code and headers spending varying amounts
of time doing the determination, it's good that the lynx community did
the examination at one point and provided a statement. And it's good
that as new code is added to lynx that code is being examined to make sure
that it keeps year 2000 compliant.
> Real reason: browsers need to do calculations on dates to determine whether
> a page has expired. In fact he should probably be asking his management
Then there's cookie handling, caching, ftp output sorted by date, etc.
--
Larry W. Virden <URL: mailto:address@hidden>
<URL: http://www.purl.org/NET/lvirden/> <*> O- "No one is what he seems."
Unless explicitly stated to the contrary, nothing in this posting should
be construed as representing my employer's opinions.