[jira] Updated: (ETCH-54) TransportFactory.newTransport returns stack topped by DeliveryService which makes it hard to implement meta transports

["scott comer (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ETCH-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

scott comer updated ETCH-54:
----------------------------

    Fix Version/s: 1.1

moving this to 1.1 as there are no complaints about doing so.

> TransportFactory.newTransport returns stack topped by DeliveryService which makes it hard to implement meta transports
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: ETCH-54
>                 URL: https://issues.apache.org/jira/browse/ETCH-54
>             Project: Etch
>          Issue Type: Improvement
>          Components: csharp-binding, java-binding
>    Affects Versions: 1.0.0, 1.0.1, 1.0.2
>            Reporter: scott comer
>            Assignee: scott comer
>             Fix For: 1.1
>
>
> To implement a meta transport, such as a transport supporting the name service, it is necessary to be able to internally construct a transport without having a MailboxManager and a DeliveryService stacked on top. For example PerfHelper.newServer calls TransportFactory.newTransport and gets back a DeliveryService which is then used to construct the remote and stub directly. The change would be for TransportFactory.newTransport to return the transport stack topped by the filter chain elements and then have PerfHelper add the MailboxManager and the DeliveryService before constructing the remote and the stub. So, the change is to move the construction of MailboxManager and DeliveryService to the generated helper code from the likes of TcpTransportFactory.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.