Hi We are currently working with Turbine 2.1. We used to have the http authentication code in our own SessionValidator, but in order to allow easy management of secure and weak screens and easy anonymous access to the application, we cleaned up the SessionValidator and moved the http authentication code to the secure default screen:
templates/screens/weak/blaa.vm templates/screens/secure/blaa2.vm modules/screens/weak/default.java modules/screens/secure/default.java As you can probably guess, the weak screen class doesn't require a login and the secure one does. We use http authentication and Digest coding in logging the user in. In these pre-Turbine 3.0 times, is it wise to stick to using a default screen? I know that Turbine 3.0 has a "classic pipeline", which supports the use of screens as well as all other modules. However, does the use of "classic pipeline" rule out the use of any new features of Turbine 3.0, or are there any performance issues involved? Mikko Karkkainen [EMAIL PROTECTED] _________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
