On 07/27/11 - 06:10:51PM, Joseph VLcek wrote:
Greg Blomquist and I have put together an Audrey design document for
the 0.4.0 effort.
It can be found here:
Although we would appreciate input from anyone I'm requesting review feedback from
the following people:
I am asking that all feedback be provided by COB one week from today, August 3, 2011. We
are already moving forward with some development according to the presented design so
direction changing feedback would be greatly appreciated as early as possible. If anyone
needs more time please let us know.
I tried to provide XML examples that align with the format outlined in past discussion.
If I missed that please let me know.
OK, so I took a look.
1) What is the <outputs> XML supposed to represent? I think this is possibly
supposed to match up with the "Parameters" explanation, but I'm not
2) During Configuration hand-off, I think we need to seriously consider
changing from a REST based API to a QMF based one. At least, we should put the
question to rest before 0.4.0. For a first implementation, using REST is fine,
but we need to make the decision (and implement it) before Iteration 4 is over.
3) In the invocation section for the examples, I'm a bit confused. The
document specifies what the Requires Parameters look like (presumably on the
wire) and then mention the environment variables that will be created
(AUDREY_VAR_service_A_param1, AUDREY_VAR_service_A_param2, etc for Example 1).
However, it then mentions that the start script will be invoked with:
Wouldn't that instead just be:
with the correct environment variables from above? Or am I missing something?
Otherwise, this seems to specify what we have been talking about, so it looks