You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "S.Uthaiyashankar (JIRA)" <ji...@apache.org> on 2008/12/22 07:08:44 UTC

[jira] Updated: (AXIS2C-1209) Current Dual-channel Implementation can never Support Certain Transports

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

S.Uthaiyashankar updated AXIS2C-1209:
-------------------------------------

    Component/s: core/transport

> Current Dual-channel Implementation can never Support Certain Transports
> ------------------------------------------------------------------------
>
>                 Key: AXIS2C-1209
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1209
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: core/transport
>            Reporter: Danushka Menikkumbura
>
> In the current dual-channel implementation, the message receiver is started before the message is handed over to the transport sender. This implementation can not support a transport receiver that depends on certain piece of information that is not available until the sender invocation phase. For an example, in AMQP, the receiver need to know the id of the queue that is should listen to and the queue id is not know until the transport sender is invoked. 
> So I think we should make the implementation such that the transport sender has the responsibility of starting the message receiver so that the sender can provide the receiver with whatever the vital information that it needs.

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