[
https://issues.apache.org/jira/browse/AMQNET-637?focusedWorklogId=717678&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-717678
]
ASF GitHub Bot logged work on AMQNET-637:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 30/Jan/22 17:34
Start Date: 30/Jan/22 17:34
Worklog Time Spent: 10m
Work Description: Havret commented on a change in pull request #18:
URL:
https://github.com/apache/activemq-nms-openwire/pull/18#discussion_r795218724
##########
File path: src/Transport/FutureResponse.cs
##########
@@ -25,8 +26,13 @@ namespace Apache.NMS.ActiveMQ.Transport
/// <summary>
/// Handles asynchronous responses
/// </summary>
- public class FutureResponse
+ public class FutureResponse : TaskCompletionSource<Response>
Review comment:
So it seems you have 2 `TCS`s to handle a single request-reply. One
should be enough.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 717678)
Time Spent: 15h 50m (was: 15h 40m)
> NMS 2.0
> -------
>
> Key: AMQNET-637
> URL: https://issues.apache.org/jira/browse/AMQNET-637
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: NMS
> Affects Versions: 1.8.0
> Reporter: Michael Andre Pearce
> Priority: Major
> Fix For: API-2.0.0
>
> Time Spent: 15h 50m
> Remaining Estimate: 0h
>
> NMS API is still at JMS 1.1 api level, this is to update the NMS api to the
> latest JMS 2.0 api
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
