[
https://issues.apache.org/jira/browse/ARIES-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amichai Rothman resolved ARIES-2122.
------------------------------------
Fix Version/s: rsa-2.0.0
Resolution: Fixed
> TCP Provider should support multiple services on a single port
> --------------------------------------------------------------
>
> Key: ARIES-2122
> URL: https://issues.apache.org/jira/browse/ARIES-2122
> Project: Aries
> Issue Type: Improvement
> Components: Remote Service Admin
> Affects Versions: rsa-1.16.1
> Reporter: Amichai Rothman
> Priority: Major
> Fix For: rsa-2.0.0
>
>
> Currently when using the TCP provider every remote service must be configured
> with a separate port on which it listens for incoming connections form remote
> proxies. This is tedious in configuring and managing when there are multiple
> services being exported, requiring tinkering with all service configurations,
> firewalls, managing the port lists manually as services are added or removed
> from an application, etc.
> It would be much more manageable (and consistent with other providers and
> server protocols) if multiple services could also be configured to use the
> same port if desired, which will enable requests to all of them to be
> multiplexed on the same connection and sorted out on the remote container
> (e.g. by sending the service id as part of the serialized invocation info).
> Backwards-compatibility can be maintained, i.e. services can still be
> configured with different ports, and only those that share the same port will
> be bunched together.
> This is orthogonal to ARIES-2121 but together they would bring this provider
> to production-grade.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
