- You can use conditional models. - You can use IF on models
if not request.controller == "public": # my logic goes here - You can go to the option B (simple separate app) - You can serve the login form as static html file http://yourapp/static/public.html - You can use lazy_tables and not worry about it. On Tue, Aug 28, 2012 at 10:52 PM, Yarin <ykess...@gmail.com> 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? > > -- > > > > --