Ok, we've been looking at adding the action to be executed before
redirecting to screen.homepage in Turbine.java but it seems like the
code is maybe a little redundant. It seems that if you just set the
screen and allow execution to continue that you get the exact same
result as you do by doing the redirect. Here is how the code would look
data.setScreen ( data.parameters.getString("screen") );
data.setAction ( data.parameters.getString("action") );
if (data.session.isNew())
{
data.setScreen(TurbineResources.getInstance()
.getString("screen.homepage"));
}
This seems to do the exact same thing as the redirect code but allows
you to later override the screen choice in SessionValidator if desired.
Am I missing something important here or is this an acceptable
optimization? I've tested it and to me it looks like you get the same
behaviour but without the extra redirect. What am I missing?
--
Kimbro Staken
Chief Technology Officer
Infostreet Inc.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
