Hi All. Not sure why this thread snapped me out of my lurking... maybe it was the introduction of yet another Context. ;-)
On May 12, 2004, at 5:06 AM, Eric Pugh wrote:
Instead, what I would like to see is a
PipelineData or PipelineContext
Instead of creating a new interface, why not just use a Map? I like the idea of decoupling the pipeline from RunData, but I don't think PipelineData, nor Peter's suggestion for RequestData add very much descriptive power.
The other option is to create a new interface, say RequestData, with a single purpose, that of passing objects along the pipeline.
public interface RequestData {
public void putObject(String key, Object obj);
public Object getObject(String key);
}
This example is just a subset of what is offered by Map. If you use Map you don't have to introduce any new concepts to the programmer, you can get() and put(), and also benefit from the rest of the Collections API. You also don't have to write any code for the interface nor for the implementation. Less code is A Good Thing.
-Eric (the other one :-)
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
