I've not used it (yet), but I think the idea is that you can define
parts of a task specification that are common to all tasks in the
prototype, and then just point each task to that prototype.
Environmental variables would be one easy example. Of course, if
you're auto-generating all the specifications then it doesn't make
much difference whether or not you repeat the same common set of
information in each spec or use the prototype feature.
What I'd like to test (hopefully in the next few days) is what
happens when a prototype and a specification both define the same
portion of a task. Let's say I have 10 environment variables common
to all tasks defined in a prototype, and another 5 that are unique
for each task and defined in the individual specs. Will those 5
overwrite the dictionary in the prototype, or is Xgrid smart enough
to append the two dictionaries (assuming all variable names are unique)?
I am having trouble finding documentation about this on the
Internet... What is the purpose of the taskPrototypes dictionary
in a batch plist?
Thanks,
Andrew Keller
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xgrid-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xgrid-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
