qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PROTON-1410) Move MessageImpl::TLS to an utility class
Date Wed, 01 Mar 2017 18:11:45 GMT

    [ https://issues.apache.org/jira/browse/PROTON-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890709#comment-15890709
] 

ASF GitHub Bot commented on PROTON-1410:
----------------------------------------

Github user tabish121 commented on the issue:

    https://github.com/apache/qpid-proton-j/pull/6
  
    Personally this doesn't seem a necessary addition to me.  I prefer to keep the management
of the encoder and decoder instances in the Qpid JMS code and wouldn't use this myself.  It
adds support code that then has to be maintained as part of the proton-j code that just means
we have to manage it later if the Encoders were say made to not require being managed as thread
locals for instance, e.g. we made them stateless 


> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message