I added a timestamp to the name so you get different entries. But why are you uniquely identifying the resource by the name instead of a unique identifier? Wouldn't this be better than throwing an exception if the entry already existed?
Marlon On 5/26/14 3:43 PM, Saminda Wijeratne wrote: > Right now it will overwrite the existing corresponding descriptor if it > exists. For now this is implemented in this way in order to allow testing. > > Once we have the update API functions introduced we can change the > implementation to throw an exception when trying to add a > compute-resource-descriptor which is already present in the registry. > > > > > On Mon, May 26, 2014 at 11:09 AM, Marlon Pierce <[email protected]> wrote: > >> Thanks, Saminda. What happens if you run "add-compute-resources.php" a >> bunch of times with the default values? >> >> >> Marlon >> >> On 5/26/14 1:42 PM, Saminda Wijeratne wrote: >>> A sample server for application catalog thrift service is deployed at >>> gw111.iu.xsede.org. You may use samples found @[1] to try out this >> service. >>> - add-compute-resources.php >>> - list-compute-resources.php >>> - list-application-interfaces.php >>> >>> Note : do not run any modified version of the samples against the sample >>> server. >>> >>> Thanks, >>> Saminda >>> >>> 1. https://github.com/SciGaP/Airavata-PHP-Client-Samples >>> >>
