Skip to content

Coexistence of C, C++, Rust, Python and JavaScript; Cryptography; Communication using bindgen, FFI, REST(HTTP), gRPC and zmq (TCP)

Notifications You must be signed in to change notification settings

adi-g15/languages-coexistence

Repository files navigation

Language Coexistence

languages-coexistence

CodeFactor

A project showcasing various languages used in a single project

Initially a Crypto... Testbed (ie. just trying out various cryptography concepts and using there libraries), ended up dividing parts to use each part in an another language, just for a fun practise

NOTE: It is INTENTIONALLY using so much for a simple goal

Coexistence of C++, Rust, JavaScript and Python. And multiple ways of calling functions from different languages:

  • C -> C (calling your parents isn't tough right ❤️)
  • C++ <-> Rust : FFI (using cbindgen)
  • Rust -> Python : REST (HTTP requests)
  • C++ <-> C++ : ZeroMQ (networking; client-server)
  • C++ -> Python : FFI (using pybind11)
  • C++ <-> JavaScript : gRPC (INCOMPLETE; networking; server-server (the C++ server contacting gRPC server so then a client actually))

CMake builds Cargo (Not exactly a language, but this was new for me, using a CMake script to build rust code triggered by CMake)

Run client --help for help.

Design Plan

Testbed

This is a testbed application (originally wasn't), so it's INTENTIONALLY much more complex than it should be... though as always I did start very simple at beginning.

For me it's a place to try some co-existence things:

  • C++ code calls methods in Rust; Used build.rs for the first time in rust to create the bindings
  • CMake builds rust code too, first time
  • Rust code and C++ both using OpenSSL (Initially was doing that part in Rust, then wanted some fun... C++)... was a first time working with OpenSSL in C++
  • Setup networking with libzmq, first time doing so in a C++ app
  • Used argparse library, first time in C++, though have used different CLI parsers earlier

Some things I have done before, but those that add a cherry on top of the cake

  • Use protocol buffers for serialisation/deserialisation
  • Using CPM.cmake... Iske baare me kya hi bole, bahut gadar hai, bahut help karta hai

Building

Since it uses a variety of tech... you may expect some dependencies, though for most developers you must have installed these sometime

Firstly install openssl, protobuf, zeromq (libssl-dev, protobuf-compiler, libzmq3-dev in apt)

NOTE: On debian systems atleast, you must install pkg-config too, it's required by CMake to search OpenSSL

Considering you have python3 (with python3-distutils, python3-dev), cargo (rust), and nodejs (javascript)...

cmake -B build
cmake --build build

Then to run:

  • Server: ./build/server
  • Client: ./build/client --help
  1. Basic study of cryptographic concepts and practising them with either javascript/python/rust libraries or Linux command CLI(sha256sum, base64, openssl),

    Encoding/Decoding

    Hashing

    Digital Signatures

    Encryption/Decryption

Extras Planned:

  • Serialisation/Deserialisation (using protobuf)

  • Digital Certificates

About

Coexistence of C, C++, Rust, Python and JavaScript; Cryptography; Communication using bindgen, FFI, REST(HTTP), gRPC and zmq (TCP)

Topics

Resources

Stars

Watchers

Forks