MartinWinkler wrote: > Hi again, > > On Jun 10, 10:37 pm, Florian Apolloner <[EMAIL PROTECTED]> wrote: > >> Why don't you display the image dynamically with django, without >> saving it? >> Example:http://django-captcha.googlecode.com/svn/trunk/djaptcha/views.py > > I already took a look at django-captcha, and what I do not like in > this solution is the amount of additional work a programmer has to > invest here. > With my approach there is just a CaptchaField for the website > developer and nothing more. No urls.py changes, no new settings, > nothing. It 'just works'. > > I'll make my little solution available soon and will use Phil's > proposal of deleting old images just before creating a new captcha. > Although it's not as elegant as I would like, because it scans the > captcha-directory whenever a new captcha image is about to be made.
I sense a race condition: browser 1 hits server: delete *.png/create a.png send img=a.png to browser 1 browser 2 hits server: delete *.png/create b.png send img=b.png to browser 2 browser 1 requestss a.png 404. Also, file IO is 'expensive.' Granted most sites don't get hammered, so for many it will not be an issue, but there should only be one way to do things. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
