The ecap-rs from mark-simulacrum

ecap-rs's Introduction

ecap-rs

This is a compatible rewrite of libecap in Rust.

This project has the following goals:

Permit adapters written in Rust to be easily used by C++ hosts, such as Squid.
Permit hosts written in Rust to use C++ adapters.

The toplevel crates are as follows:

ecap: core crate, defines traits and structs (similar to libecap itself)
ecap-common: shared library which provides service/translator registration
ecap-common-link: workaround for Cargo, shim over ecap-common so that crates don't need build scripts
ecap-cpp: translator from C++ to Rust types (currently incomplete)
ecap-sys: C API for the C++ libecap library.
adapter-minimal: minimal adapter written in Rust

ecap-rs's People

Contributors

Stargazers

Watchers

ecap-rs's Issues

Exception/Panic handling

In both directions panics and exceptions carry the same semantic meaning so they should be caught at boundaries and repropagated within each language.

We want to require only Send for adapter::{Service, Transaction}. Additionally, host::Transaction will gain a new method that returns an abstract Token that can be passed to the host to resume the transaction.

Must change host methods to take reference to adapter transaction

This is needed to prevent code like the following, since use_adapted may potentially call other &mut methods on self; as such we need to "give it" that access and permit the compiler to catch us if we're doing something non-beneficial.

fn start(&mut self, host: &mut H::TransactionRef) {
    let a = &self.field;
    let adapted = ...;
    host.use_adapted(adapted);
}

Handle predefined libecap::Names

The current theorized approach is to have the host manage the ID allocation. ecap would provide a set of helper functions which internally call into the host and return the allocated Name.

Recommend Projects