[
https://issues.apache.org/jira/browse/PROTON-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890650#comment-15890650
]
ASF GitHub Bot commented on PROTON-1410:
----------------------------------------
Github user gemmellr commented on the issue:
https://github.com/apache/qpid-proton-j/pull/6
I'm aware of what qpid-jms does, it does that while avoiding using the
Message[Impl] from proton entirely, meaning it isn't using the thread local
from there either, but just happens to have its own (though it could actually
do the same without that thread local if it wanted, given how the rest of the
client works.) I wouldnt be all that inclined to make qpid-jms use the proposed
TLSEncoder class even if it already existed in proton, it seems nicer to keep
that in the client.
As an aside, TLS seems a weird acronym to use in the name, given its
typical meaning/usage.
> Move MessageImpl::TLS to an utility class
> -----------------------------------------
>
> Key: PROTON-1410
> URL: https://issues.apache.org/jira/browse/PROTON-1410
> Project: Qpid Proton
> Issue Type: Improvement
> Reporter: clebert suconic
>
> I have a need to create a special Message on Artemis, that will only parse
> the Header and send everything else as a byte array.
> Instead of duplicating the TLS logic, I would like to move this to its own
> class so it could be reused.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
