Hi,

I am creating an application similar to basecamp. On every view I need
to do lots of book keeping such as checking to see if company exists,
user exists, user is logged in, etc. before I can do what the view is
actually there to do. That is a lot of redundancy as apposed to having
a controller that would take care of bookkeeping before my view is
loaded. What's the remedy?

One idea I had was to create a class that would take 'request'
object and takes care of redundant work and returns a dictionary
containing all the data I need which I would forward to my template.

Ideas are appreciate here,

Regards,
Mike

Reply via email to