You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Jason Kary <jk...@cisco.com> on 2001/09/13 15:50:16 UTC
ParameterParser for session?
Hi,
Has anyone thought about making the RunData interface have a method as
follows:
public ParameterParser getSession();
Would this not make the interface more consistent?
JK
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
Re: ParameterParser for session?
Posted by Sean Legassick <se...@informage.net>.
In message <3B...@cisco.com>, Jason Kary <jk...@cisco.com>
writes
>Has anyone thought about making the RunData interface have a method as
>follows:
>
>public ParameterParser getSession();
>
>Would this not make the interface more consistent?
Hi Jason.
With servlets In general, I think the expectation is that the session
will contain instances of app-specific classes. With Turbine the design
intention is that most if not all session data will be held in the User
instance's temporary hashtable via setTemp/getTemp.
Given this I can't see a compelling need for parsing of session
contents.
--
Sean Legassick
sean@informage.net
Hombre soy, nada humano me puede ser ajeno
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
Re: ParameterParser for session?
Posted by Jon Stevens <jo...@latchkey.com>.
on 9/13/01 6:50 AM, "Jason Kary" <jk...@cisco.com> wrote:
> Hi,
>
> Has anyone thought about making the RunData interface have a method as
> follows:
>
> public ParameterParser getSession();
>
> Would this not make the interface more consistent?
>
> JK
Looking at the Fulcrum/CookieParser class, I believe we already have a
data.getCookies()
-jon
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org