[
https://issues.apache.org/activemq/browse/AMQ-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42231#action_42231
]
Timothy Bish commented on AMQ-1609:
-----------------------------------
I'd think we'd want some sort of versioning of the Stomp protocol so that
clients can know what they are talking when communicating with a broker. For
instance if the ActiveMQ CPP client was to receive a stomp frame with this
property encoding we'd probably throw all sorts of exceptions which would not
be good. I'd think if we did something like this we'd need to also provide
some sort of wire format negotiation mechanism so that a client can tell the
broker whether or not it can handle v1.1 typed properties or not.
> STOMP messages only support properties with data type String
> -------------------------------------------------------------
>
> Key: AMQ-1609
> URL: https://issues.apache.org/activemq/browse/AMQ-1609
> Project: ActiveMQ
> Issue Type: Improvement
> Reporter: Michael Justin
>
> Currently the STOMP connector seems to support only string type message
> properties.
> As an effect, subscription selectors like color = 'blue' AND weight > 2500
> will not work (if the message has been sent using STOMP, the weight property
> will be a string).
> I suggest to implement typed properties in the Stomp protocol which could be
> serialized in a platform-independent way.
> In addtion , if I understand the OpenWire documentation correctly, the
> OpenWire protocol supports some simple datatypes, but not - for example -
> Date, which would be easy to map to a long value.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
