frank wrote: > Sure, I could create a download button for each > item, but that would be an extra step for the user. 'It would be nice' > if that weren't necessary. > BTW the downloads are static files, served by Apache. That extra > button > is looking more and more likely...
At some point the user is going to click on a link to download the file. What you do is make that a URL to a django app that increments a counter and then sends a redirect HTTP message to the actual file which apache then spits back. So you have a Django model called 'Downloads' with an integer 'Count' field and a text 'Filename' field. This could be initially empty... ..then your URL would be: http://mymachine.com/downloads/package/version/file-1.0.tar.gz ...then your urls.conf would match /downloads/(.*) ...the associated view then increments the counter for /package/version/file-1.0.tar.gz, or creates it if new... ...then sends a redirect (http code 304?) message to http://mymachine.com/files/package/version/file-1.0.tar.gz, which is the path to the file on the apache server. You might want to check the file exists in the Django view first ...so that the browser goes and gets that without asking the user. The only thing I'm unsure of is the exact HTTP message to send and how to get Django to do it, but it should be in the docs somewhere.... Barry --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
