Re: Best DRY practices for a view function that will be used by all other views.

Because I will have the login form on each page, I will not have a separate login URL. That's why I'm having difficulties with organizing the business logic code (i.e. view).  It's almost as if I need to have two view functions -- one for login and another for the current page -- for the URL for the current page.  I hope that makes sense.  Of course, we all know that we can't have two separate view functions for one URL, so I would have to take the login code and somehow tie it to the view for each page.  There are several ways to make this work, but my main question is:  What is the cleanest and most maintainable way for me to do this?

Thanks all for your input!

--
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 django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.