kafka-client
By abhinav
connection
simple client connection library in haskell with builtin features: SSL/TLS, SOCKS, session management. (by vincenthz)
| kafka-client | connection | |
|---|---|---|
| - | 1 | |
| 1 | 61 | |
| - | - | |
| 0.0 | 0.0 | |
| - | 10 months ago | |
| Haskell | Haskell | |
| MIT License | BSD 3-clause "New" or "Revised" License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kafka-client
Posts with mentions or reviews of kafka-client.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning kafka-client yet.
Tracking mentions began in Dec 2020.
connection
Posts with mentions or reviews of connection.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-05.
-
Crypton is forked from cryptonite with the original authors permission
Trying to build the "old" hs-connection (which is still in my my project's dependency tree) after a cabal update, I now get this : Network/Connection.hs:123:43: error: • Couldn't match expected type ‘crypton-x509-store-1.6.9:Data.X509.CertificateStore.CertificateStore’ with actual type ‘Data.X509.CertificateStore.CertificateStore’ NB: ‘crypton-x509-store-1.6.9:Data.X509.CertificateStore.CertificateStore’ is defined in ‘Data.X509.CertificateStore’ in package ‘crypton-x509-store-1.6.9’ ‘Data.X509.CertificateStore.CertificateStore’ is defined in ‘Data.X509.CertificateStore’ in package ‘x509-store-1.6.9’ • In the ‘sharedCAStore’ field of a record In the ‘clientShared’ field of a record In the expression: (TLS.defaultParamsClient (fst cid) portString) {TLS.clientSupported = def {TLS.supportedCiphers = TLS.ciphersuite_default}, TLS.clientShared = def {TLS.sharedCAStore = globalCertificateStore cg, TLS.sharedValidationCache = validationCache}} | 123 | { TLS.sharedCAStore = globalCertificateStore cg | Error: cabal: Failed to build connection-0.3.1.
What are some alternatives?
When comparing kafka-client and connection you can also consider the following projects:
json-rpc - Fully-featured JSON-RPC 2.0 library for Haskell programs
hs-twitterarchiver - Commandline Twitter feed archiver
curl - A Haskell binding to the curl library
tcp-streams - One stop solution for tcp client and server with tls support.
prometheus-client - Haskell client library for exposing prometheus.io metrics.
api-builder - library for building JSON API wrappers in haskell
tls - TLS/SSL implementation in haskell
pagerduty - Haskell PagerDuty API Client
haskoin - Haskoin Core is a Bitcoin and Bitcoin Cash library
kafka-client vs json-rpc
connection vs hs-twitterarchiver
kafka-client vs curl
connection vs json-rpc
kafka-client vs tcp-streams
connection vs prometheus-client
kafka-client vs prometheus-client
connection vs api-builder
kafka-client vs tls
connection vs tls
kafka-client vs pagerduty
connection vs haskoin