[
https://issues.apache.org/jira/browse/AIRAVATA-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453996#comment-13453996
]
Suresh Marru commented on AIRAVATA-568:
---------------------------------------
I would say thats too complicated to support interoperability with external
execution systems. I would even argue, two airavata instances should also not
check for uniqueness across them. Its not about default vs advanced option. My
concerns are mainly, this is a bad design choice to let the clients send a
unique id to a server which has serious implications if the id is not unique.
> Method to set messaging topic from airavata client
> --------------------------------------------------
>
> Key: AIRAVATA-568
> URL: https://issues.apache.org/jira/browse/AIRAVATA-568
> Project: Airavata
> Issue Type: Improvement
> Reporter: Raminderjeet Singh
>
> These need to a method to set messaging topic from airavata API for advanced
> clients to sent the information
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
