----- Original Message -----
Sent: Tuesday, December 28, 1999 10:52
AM
Subject: Re: [Zope] Dumb object aliasing
question
Sorry for the code on this list. Wasn't sure
about moving it to ZopeDev.
This fixes the problem for the outside caller.
The images change in sync with what ever you upload.
I changed > to <
self._p_mtime is the date of the object in zope
and ms is the changed since date from the browser.
OFS/image.py line: 187
# Attempt
to handle If-Modified-Since
headers.
ms=REQUEST.get_header('If-Modified-Since',
None)
if ms is not
None:
ms=string.split(ms,
';')[0]
ms=DateTime(ms).timeTime()
if self._p_mtime <
ms:
RESPONSE.setStatus(304)
return RESPONSE
If 304 is set, it means the data hasn't
changed.
304:
('Not
modified',
'Document has not changed singe given time'),
This doesn't fix it for manage
though.
I'll look at that one tonight.
--Darrell
----- Original Message -----
Sent: Monday, December 27, 1999 10:27
PM
Subject: [Zope] Dumb object aliasing
question
If I add a new image, call it img1 and view
it outside of manage, all is well. If I replace that image and view it.
It hasn't changed ?? If I view it in manage it's the new image.
Restarting Zope doesn't help.
If I now change this image in manage a second
time it won't change. But it's size changed, just not the
image.
I picked up the CVS version deleted Data.fs
and started over, with the same results. Shouldn't I be able to change an image ?
Any idea where the code is that decides to
render one way for local manage and another way for the remote user ?
I'll find it eventually ....gurrr
--Darrell