[
https://issues.apache.org/activemq/browse/AMQCPP-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39000
]
Timothy Bish commented on AMQCPP-66:
------------------------------------
Submitted the first cut of the AsyncSendTransport to Trunk.
Messages are cloned before being placed in the send queue.
> Refactor the Async send to happen in an Async Transport instead of in
> ActiveMQSession
> -------------------------------------------------------------------------------------
>
> Key: AMQCPP-66
> URL: https://issues.apache.org/activemq/browse/AMQCPP-66
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Affects Versions: 1.1, 2.0
> Reporter: Timothy Bish
> Assigned To: Timothy Bish
> Priority: Minor
> Fix For: 2.1
>
>
> We should re-factor the code that implements the Async Send feature to use an
> TransportFilter dervied class that handles the async send stuff. This would
> reduce the overhead as right now, each session creates a thread for sends,
> where this class would only need one thread and everyone would just make use
> of it.
> We need this issue to get done first I think so that we can cleanly implement
> this.
> https://issues.apache.org/activemq/browse/AMQCPP-65
> One other thing we might want to think about here is the lifetime of objects
> that are sent when in async mode. Currently all messages are cloned and
> deleted by the session. We may want to think about changing the CMS API to
> require that objects are owned by us once you pass them to a send call. Then
> we can control the lifetime and delete it when we are done with it without
> having to clone the message.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
