James Y Knight wrote:
Janne mentioned on IRC that the actual goal is to be able to ask for username/password login for some children but not others. Thus, I suspect a solution where the SessionWrapper is on the root, but is configured somehow to not require login except for certain resources would work.
I dunno how to do that but it looks probably possible from the API?
It was certainly possible with woven.guard; you could pass in two separate resources, one for anon and one for loggedin. Of course those resources could also look at the session to see if the user is logged in, then redirect to the login screen if necessary. No idea how nevow.guard works. -- Twisted | Christopher Armstrong: International Man of Twistery Radix | Release Manager, Twisted Project ---------+ http://radix.twistedmatrix.com/