On 8/9/06, Paul Sargent <[EMAIL PROTECTED]> wrote: > > > 3 is reasonably simple, but I want this to have some form of > authorization. Django's normal authorization framework seems rather > awkward, because I'd need my script to go through a login process to > get the right cookie (right?). > > Any other suggestions for authenticating in the view? > >
Hmm, I guess I would create a separate "view" which does not have any url mapped to it. As it is not available publicly (over http), do you really need any other authentication than the systems file permissions? Of course, you may need to write a little more code to make sure everything is available that you would normally get via an http request but that shouldn't be to difficult. -- ---- Waylan Limberg [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
