copying images + hit or save detection in Zope ?
Q1. Is there any reliable way to know if someone has copied an image, a file or saved an HTML page from their browser using "Save as.." or similar? Q2. If yes, how would you suggest using Zope to catch events and store statistics on this. Create a ZCatalog with an updated 'saved_hits' property for each item would be ideal. Q3. Whether it is possible or not, how would you suggest using Zope to keep count of hits to Zope pages/objects? The application is a Zope site with a lot of graphics. Contributers [Artists] will upload often, according to their schedules and whims. Designing for ecletic low-maintenance freedom here.. There will be gallery and styudio areas for browsing the art. Instead of making people jump through a bunch of tedious form actions to get their images adn to store download data on the server, I thought it might be friendlier to just tell them 'save as..' any ideas? --Jason ___________________________________________________________ Jason CUNLIFFE = NOMADICS['Interactive Art and Technology']
On Mon, 16 Apr 2001, Jason Cunliffe wrote:
Q1. Is there any reliable way to know if someone has copied an image, a file or saved an HTML page from their browser using "Save as.." or similar?
There is no - because of cacheing.
Q2. If yes, how would you suggest using Zope to catch events and store statistics on this. Create a ZCatalog with an updated 'saved_hits' property for each item would be ideal.
Each of your images should be an instance of a class that counts hits on every call.
Q3. Whether it is possible or not, how would you suggest using Zope to keep count of hits to Zope pages/objects?
There are counter Products - search zope.org. Oleg. ---- Oleg Broytmann http://www.zope.org/Members/phd/ phd@phd.pp.ru Programmers don't die, they just GOSUB without RETURN.
Q2. If yes, how would you suggest using Zope to catch events and store statistics on this. Create a ZCatalog with an updated 'saved_hits' property for each item would be ideal.
Each of your images should be an instance of a class that counts hits on every call.
Ouch expensive overhead, you can modify FSCounter for this, but really this is what log files are for. Cheers. -- Andy McKay.
On Mon, 16 Apr 2001, Andy McKay wrote:
Ouch expensive overhead, you can modify FSCounter for this, but really this is what log files are for.
Setup: /img - Folder with images standard_html_header - DTML Method that calls <img src="img/myImg.gif"> Now the log is full of access to /xxx/img/myImg.gif, /yyy/img/myImg.gif etc. But in reality this is the same image. Better do it from Zope. Oleg. ---- Oleg Broytmann http://www.zope.org/Members/phd/ phd@phd.pp.ru Programmers don't die, they just GOSUB without RETURN.
On 16 Apr 2001 20:36:42 +0400, Oleg Broytmann wrote:
On Mon, 16 Apr 2001, Andy McKay wrote:
Ouch expensive overhead, you can modify FSCounter for this, but really this is what log files are for.
Setup: /img - Folder with images standard_html_header - DTML Method that calls <img src="img/myImg.gif">
Now the log is full of access to /xxx/img/myImg.gif, /yyy/img/myImg.gif etc. But in reality this is the same image.
Better do it from Zope.
Or simply change the URL. If you call images by their absolute URL whenever possible you will not only make it easier to count them in your logfiles, but you will also help the browser cache properly. When the browser (and web proxies) see relative urls such as above, they have to retreive the new relative image, since they don't realize they already have the image. if you use the method I propose (and use, btw), they see an absolute path, and having already retreived that image, use the cache. So, you could put all your images in /img and then call <img src="/img/myImg.jpg">, and save bandwidth as well as zope processing. :) Bill
participants (4)
-
Andy McKay -
Bill Anderson -
Jason Cunliffe -
Oleg Broytmann