You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Mark Eschbach (JIRA)" <ji...@apache.org> on 2010/07/17 00:56:51 UTC
[jira] Created: (AMQ-2833) Fix to STOMP Transport fixing message
type selection
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
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.
[jira] Resolved: (AMQ-2833) Fix to STOMP Transport fixing message
type selection
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies resolved AMQ-2833.
-----------------------------
Fix Version/s: 5.4.0
Resolution: Fixed
Patch applied in SVN revision 965542
> 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
> Assignee: Rob Davies
> Priority: Minor
> Fix For: 5.4.0
>
> Attachments: stomp-msg-type.patch
>
>
> 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.
[jira] Updated: (AMQ-2833) Fix to STOMP Transport fixing message
type selection
Posted by "Mark Eschbach (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (AMQ-2833) Fix to STOMP Transport fixing message
type selection
Posted by "Mark Eschbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Eschbach updated AMQ-2833:
-------------------------------
Original Estimate: (was: 20 minutes)
Remaining Estimate: (was: 20 minutes)
I cleared the estimated time as I misunderstood what the field would indicate.
> 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
>
>
> 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.
[jira] Assigned: (AMQ-2833) Fix to STOMP Transport fixing message
type selection
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies reassigned AMQ-2833:
-------------------------------
Assignee: Rob Davies
> 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
> Assignee: Rob Davies
> Priority: Minor
> Attachments: stomp-msg-type.patch
>
>
> 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.