In TurbineResources there is a screen.homepage property but there is no
corresponding action.homepage. Is there a reason for this? The reason I
am asking is that we will be running multiple apps across multiple
servlet engines but we do not want to require people to have to log in
again when crossing servers. We can set a cookie that will get sent to
all servers and can be used to initialize their session but Turbine.java
always redirects to screen.homepage if there is no session. It would be
nice if there was also an action.homepage that could be called first to
determine whether the homepage screen should be shown or not. In our
case we would just want to create the session using the cookie if it
exists and continue processing the request normally. Obviouslly we could
put this logic into the screen set for screen.homepage but it seems like
the wrong place. Is my understanding correct here? Is this something
that would be acceptable to add? I'll of course contribute the change if
it is but I'm open to other ideas if I'm on the wrong path.
Thanks
--
Kimbro Staken
Chief Technology Officer
Infostreet Inc.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
