activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Pollack (JIRA)" <jira+amq...@apache.org>
Subject [jira] Commented: (AMQNET-101) Support System.Messaging.MessagePriority
Date Tue, 12 Aug 2008 18:46:52 GMT

    [ https://issues.apache.org/activemq/browse/AMQNET-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44934#action_44934
] 

Mark Pollack commented on AMQNET-101:
-------------------------------------

There are only 8 enums in MessagePriority and 10 is the range in the spec.  As some providers
may implement priority delivery 'exactly' on this scale, it would break the contract to map
to less than 10 values.

IMHO, it also seems not worth it in terms of readability as compared to having to have system.messaging
as a dependency everywhere...  

> Support System.Messaging.MessagePriority
> ----------------------------------------
>
>                 Key: AMQNET-101
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-101
>             Project: ActiveMQ .Net
>          Issue Type: Improvement
>          Components: ActiveMQ Client, EMS, MSMQ, Stomp
>    Affects Versions: 1.1
>            Reporter: Jim Gomes
>            Assignee: Jim Gomes
>             Fix For: 1.1
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> The Priority field on IMessageProducer, and IMessage is currently an untyped byte.  It
would be better to integrate with .NET System.Messaging.MessagePriority enumeration to make
the code more readable and have a more .NET behavior.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message