[
https://issues.apache.org/jira/browse/AXIS2C-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2C-1327.
-------------------------------------
Resolution: Won't Fix
The dual-channel async pattern was designed for HTTP/1.1 limitations. With
HTTP/2's
multiplexing, separate listener channels are unnecessary, making this
enhancement obsolete
for the primary use case of Axis2/C 2.0.0.
> Providing resource free callback in Dual channel non blocking scenarios
> -----------------------------------------------------------------------
>
> Key: AXIS2C-1327
> URL: https://issues.apache.org/jira/browse/AXIS2C-1327
> Project: Axis2-C
> Issue Type: Improvement
> Components: core/engine
> Reporter: Damitha N.M. Kumarage
> Priority: Major
>
> In dual channel non blocking scenarios user pass callback with callback on
> complete function set. However in case where
> application programmer need to free resources(like stub, axis2 environment)
> per call basis he cannot do so even after his
> on complete function is called because shared resources still may be used by
> Axis2/C engine. To avoid this it is suggested
> in the mail thread[1] that a second resource free callback may be provided by
> the client application programmer
> which will be called by the Axis2/C engine once it is ready to free resources.
> [1] http://marc.info/?t=122899247800001&r=1&w=2
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
