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.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
