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 "Danushka Menikkumbura (JIRA)" <ji...@apache.org> on 2008/06/29 11:43:45 UTC
[jira] Created: (AXIS2C-1209) Current Dual-channel Implementation
can never Support Certain Transports
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
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Commented: (AXIS2C-1209) Current Dual-channel Implementation
can never Support Certain Transports
Posted by "Damitha Kumarage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609208#action_12609208 ]
Damitha Kumarage commented on AXIS2C-1209:
------------------------------------------
Currently listener manager is started at the service client code when it is using send_receive_non_blocking with separate listener. Since this is done for each request it would do no harm to move this functionality into the sender. From the sender, according to the MEP and use separate listner option we can start it.
Also currently when creating or starting listener manager we do not pass any transport specific paraemter list. You would also need to change listener manager code to allow that. We need to pass that information into the loaded transport implementation.
+1 from me for moving listener mansger sartup functionlity into sender with the above change.
> 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
> 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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Updated: (AXIS2C-1209) Current Dual-channel Implementation
can never Support Certain Transports
Posted by "S.Uthaiyashankar (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (AXIS2C-1209) Current Dual-channel Implementation
can never Support Certain Transports
Posted by "Damitha Kumarage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609212#action_12609212 ]
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 https://svn.apache.org/repos/asf/webservices/axis2/trunk/c https://svn.apache.org/repos/asf/webservices/axis2/branches/c/axis2c_listener_manager_changes-30june2008 -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: https://issues.apache.org/jira/browse/AXIS2C-1209
> 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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org