Sean Legassick wrote:
> On Tue, Feb 20, 2001 at 12:30:01PM -0500, Jason van Zyl wrote:
>
>> Hi,
>>
>> I just updated tambora with the lastest turbine and I
>> noticed that setResponse() isn't in the RunData interface
>> and that setResponse() in TurbineRunData is protected?
>>
>> Is this an oversight?
>
>
> I think at the time that RunData was made an interface, Ilkka commented
> that he may have removed some setXXX methods that were needed. I'm sure
> it should just be added...
>
In any case, setResponse() looks dangerous. For instance, we have a portlet in
Jetspeed that can display
a Turbine screen in a window. This is, obviously, if the screen does not call
setResponse().
Having this method public looks dangerous to me.
Is there a good reason to change the HTTP response outside of the "core" turbine code?
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
