[
https://issues.apache.org/jira/browse/THRIFT-3369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935174#comment-15935174
]
James E. King, III commented on THRIFT-3369:
--------------------------------------------
I'm okay following the precedent set forth in the C++ library build. OpenSSL
is a requirement there, why shouldn't it also be a requirement here?
Alternatively, one could look at the C++ library itself as being the
misbehaving component, and claim it needs to be changed to allow openssl to be
optional as well.
If this needs to be fixed then the OpenSSL transport stuff needs to link into a
separate link library, much like how C++ handles zlib or libevent.
> Implement SSL/TLS support on C with c_glib
> ------------------------------------------
>
> Key: THRIFT-3369
> URL: https://issues.apache.org/jira/browse/THRIFT-3369
> Project: Thrift
> Issue Type: Improvement
> Components: C glib - Library
> Affects Versions: 0.9.1, 0.9.2, 0.9.3, 1.0
> Reporter: Gonzalo Aguilar
> Assignee: James E. King, III
> Labels: features, patch
> Fix For: 0.11.0
>
>
> Implement SSL/TLS based on plain openssl instead of going through the way
> defined in THRIFT-1016.
> This help us to maintain a reference implementation and later switch over GIO
> or whatever is defined. But also does not add any other dependencies to the
> project. So bare minimum installation for supporting SSL/TLS is there and
> aligned with CPP counterpart.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
