I understand the purpose, the vision of the change. It's just that after
todays testing I think that this will be a big problem for the ones
migrating from 2.3.3 to 4.0.
I don't excpect this to be changed back but I do think the change should be
reconsidered. Right now my opinion is that the cons outweigh the pros.
/Ludwig
-----Ursprungligt meddelande-----
From: Thomas Vandahl
Sent: Saturday, June 25, 2011 8:40 PM
To: Turbine Developers List
Subject: Re: [VOTE] Release turbine-4.0-M1 based on RC3
Am 25.06.2011 18:54, schrieb Ludwig Magnusson:
Is there any good reason why PipelineData should be used in the modules?
(Some things guessed from intepreting the intention and the implementation)
From what I see, PipelineData is to replace RunData as a request
object. In the pipeline it is possible to modify the execution of a
request, so in the future, PipelineData might support the processing of
totally different request types. I guess it was meant to be a more
generic concept. The idea has been derived from the Catalina pipeline
IIRC. It has been implemented in the Turbine-3 branch first which was
used in Scarab. Maybe some code-digging there would shed more light on
the topic.
Bye, Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
