[
https://issues.apache.org/jira/browse/AMQNET-637?focusedWorklogId=449993&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-449993
]
ASF GitHub Bot logged work on AMQNET-637:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 23/Jun/20 19:44
Start Date: 23/Jun/20 19:44
Worklog Time Spent: 10m
Work Description: Havret edited a comment on pull request #56:
URL: https://github.com/apache/activemq-nms-amqp/pull/56#issuecomment-648378968
@cjwmorgan-sol So sends are fire and forget in AmqpNetLite. To be precise
all IO operations are fire and forget. You do not actually await any IO
operation. Take a look at this -->
https://github.com/Azure/amqpnetlite/issues/415. All you can await for in sync
or async way is a reply from the broker itself. I'm not sure what it has to do
with the order of messages, though.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 449993)
Time Spent: 7h 10m (was: 7h)
> 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: 2.0.0
>
> Time Spent: 7h 10m
> 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.3.4#803005)
