[ 
https://issues.apache.org/jira/browse/AMQNET-589?focusedWorklogId=276129&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-276129
 ]

ASF GitHub Bot logged work on AMQNET-589:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 12/Jul/19 20:17
            Start Date: 12/Jul/19 20:17
    Worklog Time Spent: 10m 
      Work Description: cjwmorgan-sol commented on pull request #4: AMQNET-589: 
Failover implementation
URL: https://github.com/apache/activemq-nms-amqp/pull/4#discussion_r303134303
 
 

 ##########
 File path: src/NMS.AMQP/Message/Facade/INmsMessageFacade.cs
 ##########
 @@ -15,47 +15,28 @@
  * limitations under the License.
  */
 using System;
-using System.Collections.Generic;
-using System.Linq;
-using System.Text;
-using System.Threading.Tasks;
-using Apache.NMS;
 
-
-namespace Apache.NMS.AMQP.Message.Cloak
+namespace Apache.NMS.AMQP.Message.Facade
 {
-    /// <summary>
-    /// Provider specific Cloak Interface from provider implementation.
-    /// </summary>
-    interface IMessageCloak : IMessage
+    public interface INmsMessageFacade
     {
-        byte[] Content
-        {
-            get;
-            set;
-        }
-
-        bool IsBodyReadOnly { get; set; }
-
-        bool IsPropertiesReadOnly { get; set; }
-
-        bool IsReceived { get; }
-
-        IMessageCloak Copy();
-
-        object GetMessageAnnotation(string symbolKey);
-
-        void SetMessageAnnotation(string symbolKey, object value);
-
-        object GetDeliveryAnnotation(string symbolKey);
-
-        void SetDeliveryAnnotation(string symbolKey, object value);
-
+        NmsMessage AsMessage();
+        void ClearBody();
         int DeliveryCount { get; set; }
-
         int RedeliveryCount { get; set; }
-
-        MessageAcknowledgementHandler AckHandler { get; set; }
-        
+        void OnSend(TimeSpan producerTtl);
+        string NMSMessageId { get; set; }
+        IPrimitiveMap Properties { get; }
+        string NMSCorrelationID { get; set; }
+        IDestination NMSDestination { get; set; }
+        TimeSpan NMSTimeToLive { get; set; }
+        MsgDeliveryMode NMSDeliveryMode { get; set; }
+        MsgPriority NMSPriority { get; set; }
+        bool NMSRedelivered { get; set; }
+        IDestination NMSReplyTo { get; set; }
+        DateTime NMSTimestamp { get; set; }
+        string NMSType { get; set; }
+        DateTime Expiration { get; set; }
+        double JmsMsgType { get; }
 
 Review comment:
   Why the type double for JmsMsgType? The qpid implementation uses a signed 
byte. I found using Helloworld the JMS msg type annotation is of type is 
double. This breaks the JMS to amqp bind mapping restriction Section 3.2.4.1 
for sending messages where the msg type annotation must be of type byte (signed 
byte if you want to inter-operable with qpid jms though). 
   I would suggest changing the type of the JmsMsgType to sbyte (and everywhere 
else). Unless there is a very good reason not to.
   ```suggestion
           sbyte JmsMsgType { get; }
   ```
 
----------------------------------------------------------------
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:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 276129)
    Time Spent: 3.5h  (was: 3h 20m)

> NMS AMQP Failover implementation
> --------------------------------
>
>                 Key: AMQNET-589
>                 URL: https://issues.apache.org/jira/browse/AMQNET-589
>             Project: ActiveMQ .Net
>          Issue Type: Improvement
>          Components: ActiveMQ, AMQP, NMS
>    Affects Versions: 1.8.0
>            Reporter: Krzysztof Porebski
>            Priority: Major
>          Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> Implement failover in NMS AMQP the same way as it is implemented in QpidJMS. 
> This will involve some major rework, as current design is too rigid to 
> introduce this feature. 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to