[
https://issues.apache.org/jira/browse/AIRAVATA-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454068#comment-13454068
]
Suresh Marru commented on AIRAVATA-568:
---------------------------------------
Yes there is a discussion about all multiple ids' but lets confuse with the
design complain I have. What ever ID it is, the server which has concerned with
unique ness, issues that ID. So yes even though a topic is used for
communication, its responsibility of the message broker to ensure its unique,
so its responsible for generating and issuing a topic id and not the client.
For Airavata case, since the deployment is bundled with all services, all of
them are collectively issuing one unique id. If there is a need to have
multiple id's we should discuss them, but still those multiple id's should be
issued by servers which have to enforce uniqueness.
> 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
