> Can someone please take a look at the changes I've made? If they are
> acceptable can they be rolled into the current versions? If not can
> they be used as a basis for a fix?
Please ignore this request. I've decided that this is an
inappropriate forum for and am logging a bug report instead
> It might be better to change the code so that the getLastModified
> and exists can be rolled into one method, returning a does not
> exist (1), comms error (2), lastModified unknown (3) or
> lastModified time (4). It can then choose to ignore the information
> for 2 and 3 but not 1 and 4. This
> Would it be possible to solve this problem by recognizing the
> communication
> failure, marking it with a special value in lastModified, and
> doing nothing
> until a real response was obtained?
The only problem is that this isn't a communication failure. The
request is getting to the serve
Would it be possible to solve this problem by recognizing the communication
failure, marking it with a special value in lastModified, and doing nothing
until a real response was obtained?
Thanks
david jencks
On 2002.08.21 06:25:09 -0400 Kevin Conner wrote:
> There has been some talk over the l
