synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sajini De Silva (JIRA)" <>
Subject [jira] [Updated] (SYNAPSE-914) Hierarchical proxy services for synapse
Date Wed, 03 Oct 2012 04:48:07 GMT


Sajini De Silva updated SYNAPSE-914:

    Attachment: hierarchical-proxy-service.patch
> Hierarchical proxy services for synapse
> ---------------------------------------
>                 Key: SYNAPSE-914
>                 URL:
>             Project: Synapse
>          Issue Type: Improvement
>          Components: Proxy Services
>         Environment: synapse
>            Reporter: Sajini De Silva
>            Priority: Minor
>         Attachments: hierarchical-proxy-service.patch
> At the moment SYNAPSE supports proxy services that can only be added under 8280:services/FooProxy
etc. Therefore it is very hard to manage the proxy services for a large organization when
the number of services become large, since they have to agree on service name before deploying
them. And also supporting multiple versions of the same service is not possible without changing
the service name in the services.xml file.
> I have  implemented  the task of supporting hierarchical proxy services in SYNAPSE. Now
when a proxy service is added other than the name of the proxy service, service hierarchy
can be inserted. If we deploy a proxy service named "foo" with a service hierarchy "a/b/c/"
in the SYNAPSE_HOME/repository/conf/synapse-config/proxy-services/a/b/c directory, you can
access that service from 8280:services/a/b/c/foo. 
> Here is the configuration for the proxy service named "foo" with a service hierarchy
>  <proxy name="foo"
>           serviceHierarchy="a/b/c/"
>           transports="https http"
>           startOnLoad="true"
>           trace="disable">
>       <description/>
>       <target>
>          <endpoint>
>             <address uri="http://localhost:9000/services/SimpleStockQuoteService"/>
>          </endpoint>
>       </target>
>    </proxy>

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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message