Timothy Bish commented on ARTEMIS-1267:

While it would be nice to avoid decoding the full message one bit that makes 
this a bit hard is that the server will peek into message annotations for each 
message to check not only for the routing type but also to see if a message has 
a delivery delay specific. You can avoid the routing type lookup by figuring 
that out ahead of time on the inbound link but the delay bits are hard to 
avoid. You might be able to avoid that if you knew the delay feature as disable 
as it could be in 5.x but otherwise I'm not sure how we'd factor that out.

> Avoid certain Map parsings on AMQPMessage
> -----------------------------------------
>                 Key: ARTEMIS-1267
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1267
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: AMQP
>    Affects Versions: 2.1.0
>            Reporter: clebert suconic
>            Assignee: clebert suconic
>            Priority: Blocker
>             Fix For: 2.3.0
> there are a few map parsers on AMQPMessage that could be avoided... 
> ... we currently parse ApplicationProperties if no Properties are defined.. 
> only to throw it away.
> ... we currently parse MessageAnnotations to throw away also.. because of 
> getAnnotation Properties on Message.type
> We could avoid all that by:
> - reading the ID of the section ahead.
> - using the destination type on the producer instead of the Message.. and 
> only use the message on the case of an anonymous producer.

This message was sent by Atlassian JIRA

Reply via email to