Hi,
> I'm trying to implement a system with Turbine where some
> screens are available without requiring the user to log in and
> some require the user to log in.
> What would be the best way to achieve this?
I'm not sure about the "best way", but what we're currently trying is the following
(which is based on the Jyve solution in which all screens are public).
This is done using Turbine and ECS alone - none of this fancy-wancy WebMacro malarky.
:-)
We have our own SessionValidator that determines whether the screen is public or
secure, if it is public, then setup a dummy user and let them through, otherwise, make
sure the user has logged in - if they havn't, then send them to the login page.
The determination of secure/public is done by hard coding a simple list of screens
that are public - if the screen is not in the list, then its secure.
Obviously soft coding the list of screens would be better, but this way all screens
are coded as standard Screen subclasses.
Any other suggestions?
Regards,
Chris
"There is no spoon"
______________________________________________
FREE Personalized Email at Mail.com
Sign up at http://www.mail.com/?sr=signup
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
