...Or to put my earlier question a different way, what's the "right" or easy way to accomplish that kind of part-public, part-login-protected design in GAE?
On Thu, Apr 29, 2010 at 09:27, Craig Berry <[email protected]> wrote: > I am building a GAE app which acts something like a CMS. Authenticated > users in a particular set can manipulate content in the datastore, but > anyone can see a page that is a read-only view of that data. I'd > really like the latter page to be truly public, not requiring > authentication to view. Is there a way to control the requirement for > authentication by URL within a single app? > > I'm using Java, if that matters. > > -- > Craig Berry - http://lapidum.org/home.html > "Magicians lie to the universe, and the > universe believes them." -- Lenore Berry > -- Craig Berry - http://lapidum.org/home.html "Magicians lie to the universe, and the universe believes them." -- Lenore Berry -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
