activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Eschbach (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-2833) Fix to STOMP Transport fixing message type selection
Date Fri, 16 Jul 2010 22:58:52 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-2833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mark Eschbach updated AMQ-2833:
-------------------------------

    Attachment: stomp-msg-type.patch

This patch provides the describe 'amq-msg-type' feature.

> Fix to STOMP Transport fixing message type selection
> ----------------------------------------------------
>
>                 Key: AMQ-2833
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2833
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Transport
>         Environment: STOMP clients which always sets the content-length header in out
going messages
>            Reporter: Mark Eschbach
>            Priority: Minor
>         Attachments: stomp-msg-type.patch
>
>   Original Estimate: 20 minutes
>  Remaining Estimate: 20 minutes
>
> Ruby's STOMP client always sets the content-length header and does not provide a mechanism
to override the behavior.  In addition, the 1.0 STOMP specification states the content-length
header is optional but recommended.  I implemented the feature discussed in AMQ-739 utilizing
the 'amq-msg-type' header to select the message type.  I've only implemented 'text' and 'byte'
message types.

-- 
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