oops, for some reason my email client sent it to Kevin directly, not to the
list... so I'll resend it.

And I was thinking a little bit more about this... Maybe we should provide
two "configuration" objects:
1. something like Rundata that contains all request specific information,
name could be "RequestData" for example. We could base this object on
RunData, but I think it would be good idea to code all the portlets against
Jetspeed interfaces, not Turbine specific RunData.
2. PortletConfig that would contain all the data that is specific to that
portlet and doesn't change between requests.

Then you would pass in to portlets this RequestData and PortletConfig would
be obtainable from this object (e.g. RequestData.getPortletConfig()).

What do you think?

Neeme

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 07, 2000 2:29 AM
> To: JetSpeed; [EMAIL PROTECTED]
> Subject: Re: multithreading problems in the portlet drawing?

[snip]

> > I think we should keep passing the rundata down in every
> getContent(),
> > or else, passing a new
> PortletConfig/PortletControllerConfig down with
> > every request. If we do not do so, there is a risk we mix
> up sessions.
> > THis is if I understand correctly the code and the sobject model, of
> > which I'm not completely sure.
>
> I would vote for passing RunData.  This means less object generation.
>
> > I know that is a major change, but we should make sure we are doing
> > things right.
>
> *totally*  +1

I remember you having a idea of abstracting away the current Turbine
infrastructure...? This is what PortletConfig is meant for? I would vote to
pass PortletConfig... but maybe we need to change the implementation of
PortletConfig so it doesn't wrap RunData, but rather copies the relevant
parts (like parameterparser)...?

And Jetspeed should have it's own ParameterParser also, that would allow us
to guarantee non-conflicting fieldnames for portlet forms... I wrote about
it in a thread in Avalon list, probably should forward that post to this
list also...

Neeme



--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Archives and Other:  <http://java.apache.org/main/mail.html>
Problems?:           [EMAIL PROTECTED]

Reply via email to