[
https://issues.apache.org/jira/browse/AXIS2C-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2C-1209.
-------------------------------------
Resolution: Won't Fix
1. No practical impact - AMQP transport doesn't exist anymore in Axis2/C;
HTTP transports work
correctly with current implementation
2. HTTP/2 is the future - The primary transport going forward uses
multiplexed connections,
not dual-channel patterns
3. Speculative enhancement - The issue describes a theoretical limitation for
a transport
that was never implemented
4. Risk vs. benefit - Changing the dual-channel lifecycle would risk breaking
existing HTTP
dual-channel functionality for zero practical benefit
If a future transport (e.g., HTTP/3 over QUIC) needs sender-controlled
receiver startup, it
would be better addressed through the interface pattern approach used for
HTTP/2, not by
modifying the legacy dual-channel architecture.
> 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
> Priority: Major
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
