axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Damitha Kumarage (JIRA)" <>
Subject [jira] Commented: (AXIS2C-1209) Current Dual-channel Implementation can never Support Certain Transports
Date Mon, 30 Jun 2008 12:01:45 GMT


Damitha Kumarage commented on AXIS2C-1209:

If you are going to do these changes I suggest you to do them in a separate branch until the
current release is over. For example you can do create the branch like this.

svn copy
-m "Making changes to listner manager to support different transports"

Later after the release we can merge this into trunk.

> Current Dual-channel Implementation can never Support Certain Transports
> ------------------------------------------------------------------------
>                 Key: AXIS2C-1209
>                 URL:
>             Project: Axis2-C
>          Issue Type: Bug
>            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.

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

View raw message