How about something like http:// <http://%3c...deployed_host_path...%3e/airavata/services/registry/> <...deployed_host_path...>/airavata/services/registry/ (Dropping the -api makes sense as whatever is accessible should be an api)
http:// <http://%3c...deployed_host_path...%3e/airavata/services/experiment/> <...deployed_host_path...>/airavata/services/experiment/ If we have a sample webapp deployed or if we decide to add anything else later on, it can go like http:// <http://%3c...deployed_host_path...%3e/airavata/%7b%7bwebappname%7d%7d/> <...deployed_host_path...>/airavata/{{webappname}}/ Viknes From: Saminda Wijeratne [mailto:[email protected]] Sent: Wednesday, August 07, 2013 11:07 PM To: [email protected]; [email protected] Subject: Re: Changing the registry rest service context & url Perhaps the following could be a better URL pattern, http:// <http://%3c...host_path...%3e/airavata-services/user-store/> <...host_path...>/airavata-services/user-store/.... http:// <http://%3c...host_path...%3e/airavata-services/registry/> <...host_path...>/airavata-services/registry/.... http:// <http://%3c...host_path...%3e/airavata-services/experiment/> <...host_path...>/airavata-services/experiment/.... eg: http:// <http://%3c...host_path...%3e/airavata-services/experiment/execution/workflo w?templateId=xxx> <...host_path...>/airavata-services/experiment/execution/workflow?templateId =xxx.... http:// <http://%3c...host_path...%3e/airavata-services/experiment/execution/cancel? experimentId=xxx> <...host_path...>/airavata-services/experiment/execution/cancel?experimentId =xxx http:// <http://%3c...host_path...%3e/airavata-services/experiment/execution/suspend ?experimentId=xxx> <...host_path...>/airavata-services/experiment/execution/suspend?experimentI d=xxx http:// <http://%3c...host_path...%3e/airavata-services/experiment/execution/resume? experimentId=xxx> <...host_path...>/airavata-services/experiment/execution/resume?experimentId =xxx On Wed, Aug 7, 2013 at 12:42 PM, Suresh Marru <[email protected] <mailto:[email protected]> > wrote: This makes good sense and probably about time to do it as well. + 1 for the change. Suresh On Aug 7, 2013, at 11:59 AM, Saminda Wijeratne <[email protected] <mailto:[email protected]> > wrote: > Hi devs, > > With the introduction of the rest service for experiment execution I think we need to have a proper service hosting url mechanism. Current registry rest service is hosted as, > http:// <http://%3c...deployed_host_path...%3e/airavata-registry/api/> <...deployed_host_path...>/airavata-registry/api/.... which I changed to, > http:// <http://%3c...deployed_host_path...%3e/airavata-services/registry-api/> <...deployed_host_path...>/airavata-services/registry-api/.... > > > Following is how we can have the new experiment service url > http:// <http://%3c...deployed_host_path...%3e/airavata-services/experiment-service/ > <...deployed_host_path...>/airavata-services/experiment-service/.... > > This is not finalized. Your thoughts are welcome. > > Regards, > Saminda
smime.p7s
Description: S/MIME cryptographic signature
