[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [sdd] Alternate definition of artifact
This proposal depends on the definition of payload. You seem to be defining it as only the solution content that is so closely similar to the resulting solution resources that people think of it as the same thing.
Note that even when the package content is closely similar to the deployed resource, it is never the same thing. A file in a package is not the same thing as a file created in a filesystem. To my thinking, all of the content of a solution package is instructions for creating the solution. The instructions might happen to be a list of the exact bits that will be created on the file system - for example, a readme file that gets created in a particular location by copying the set of bits included in the solution package. I don't yet see any value in distinguishing between instructions that are closely similar to the resulting resource and instructions that are clearly different from the resulting resource. And since I don't see value in that distinction, I am not inclined to define payload as only the solution content that is closely similar to the resulting solution resources. Which means I am not inclined to agree with your proposal.
Julia McCarthy
Tivoli Development
Deployment Engine Design
julia@us.ibm.com
349/8156
877-261-0391
"Josh Allen" <jallen@macrovision.com>
04/19/2006 07:23 PM |
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]