If you haven't determined a performance issue, best to not worry about it
("premature optimization -> evil").
On Tuesday, August 28, 2012 6:52:12 PM UTC-7, Yarin wrote:
>
> A basic architecture question:
>
> We're putting together a typical web app where non-logged in users reach a
> public-facing basic 'brochure' site, and then log in to reach the 'real'
> application. With such a setup, it makes no sense to be loading models for
> the public portion of the site, as it's just some semi-static pages and a
> login form. So I'm wondering
>
> - a) Is there a way to prevent models loading at the request or
> controller level?
> - b) Should the 'public' site be part of the same application at all,
> or should it be a separate light-weight application with a login form that
> then points to the 'real' application?
>
>
--
