Why is a SourceDataLine called “source” and a TargetDataLine called “target” though its actually the other way round?
Well, nobody really knows why this fancy naming was chosen. From the perspective of an application, it’s counter-intuitive. To understand it, take the perspective of a Mixer object: It receives data from the application via a SourceDataLine object, this is its source of data. And it delivers data to the application via a TargetDataLine. So from the perspective of the Mixer, this is the target of its data.
Related Questions
- Features and Benefits 2.1 Source Information 2.2 Target Information 2.3 ETL Process 2.4 Scalability 2.5 Lifecycle Management 2.6 Metadata 2.7 Benefits 2.1 Source Information 2.1.1 Which sources are supported by Warehouse Builder?
- Why is a SourceDataLine called "source" and a TargetDataLine called "target" though its actually the other way round?
- What happens if the 15% source energy reduction target is not met after the Post-Construction benchmarking?
