henet alternatives and similar packages
Based on the "FFI" category.
Alternatively, view henet alternatives based on common mentions on social networks and blogs.
H9.8 0.0 henet VS HThe full power of R in Haskell.
curryrs9.7 0.0 henet VS curryrsBridge the gap between Haskell and Rust
inline-java9.7 0.0 henet VS inline-javaHaskell/Java interop via inline Java code in Haskell modules.
inline-c9.7 0.0 henet VS inline-cWrite Haskell source files including C code inline. No FFI required.
zeromq-haskell9.4 0.0 henet VS zeromq-haskellBindings to ZeroMQ 2.1.x
OpenCL9.2 0.0 henet VS OpenCLHaskell high-level wrapper for OpenCL
inline-c-cpp8.8 0.0 henet VS inline-c-cppLets you embed C++ code into Haskell.
bindings-DSL8.4 0.0 henet VS bindings-DSLLibrary and macros to simplify writing Haskell FFI code
foreign-var6.0 0.0 henet VS foreign-varForeign variables, deprecated in favor of `StateVar`
bindings-svm6.0 0.0 henet VS bindings-svmLow level bindings to libsvm
bindings-libusb5.5 0.0 henet VS bindings-libusbLow level bindings to libusb
bindings-lxc5.2 0.0 henet VS bindings-lxcDirect Haskell bindings to LXC (Linux containers) C API.
statgrab5.0 0.0 henet VS statgrabHaskell bindings to the portable system statistics libstatgrab library.
bindings-levmar4.4 0.0 henet VS bindings-levmarLow level Haskell bindings to the C levmar (Levenberg-Marquardt) library
OpenCLWrappers4.4 0.0 henet VS OpenCLWrappershaskell wrappers for OpenCL
hmatrix-gsl-stats3.9 0.0 henet VS hmatrix-gsl-statsGSL Statistics functions for Haskell hmatrix
bindings-gobject3.9 0.0 henet VS bindings-gobjectLow level binding supporting GObject and derived libraries
modulo3.6 0.0 henet VS moduloModular C code generator
missing-foreign3.4 0.0 henet VS missing-foreignConvenience functions for FFI work in Haskell
storable-static-array3.1 0.0 henet VS storable-static-arrayStatically-sized array wrappers with Storable instances for FFI marshaling
bindings-wlc2.8 0.0 henet VS bindings-wlcHaskell bindings for wlc
fixed-storable-array2.5 0.0 henet VS fixed-storable-arrayfixed-size StorableArray wrapper with its own Storable instance
heatshrink2.1 0.0 henet VS heatshrinkCompression and decompression using heatshrink
haroonga2.1 0.0 henet VS haroongaLow level binding for Groonga.
bindings-sc31.6 0.0 L5 henet VS bindings-sc3Haskell bindings to the SuperCollider synthesis engine
Access the most powerful time series database as a service
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of henet or a related project?
ENet is a networking library on top of UDP. In it's own words:
ENet's purpose is to provide a relatively thin, simple and robust network communication layer on top of UDP (User Datagram Protocol). The primary feature it provides is optional reliable, in-order delivery of packets.
ENet omits certain higher level networking features such as authentication, lobbying, server discovery, encryption, or other similar tasks that are particularly application specific so that the library remains flexible, portable, and easily embeddable.
This library contains both bindings and a slightly cleaned up interface on
top. The bindings are as close to the original as possible. Names are striped of
enet_ and converted to CamelCase, and the occasional newtype is
used instead, but otherwise all functions signatures are exactly the same. The
bindings are in
The higher level interface is all other exposed modules. Functions like
enet_host_* are placed in
Network.ENet.Host. All functions are present
except for the
enet_socket* functions: they are just wrappers of the Posix
Sockets Interface, which is already provided in Haskell by the
package. Changes are fairly minimal: "Out-Args" are now returned with a tuple,
conversions between C and Haskell types happen automatically (when Haskell
versions exists), and nullable pointer types have been replaced with Maybes. In
short, there should be very few reasons to use the raw bindings over the "nice"
At the moment, consult the ENet website for documentation. In the vast majority of cases the documentation there should apply here exactly, I will try to add Haddock documentation for everywhere it does not.
ENet currently only supports IPv4 at the moment (though that should soon change), and is only safe to use as when used in one thread. Richer native networking libraries leveraging Haskell's strengths exist, and for new projects I'd recommend those. But for interfacing with existing protocols using ENet, this package should be quite useful.
- ENet website: http://enet.bespin.org
- ENet source: https://github.com/lsalzman/enet