15 releases (7 breaking)

0.8.1 May 1, 2023
0.7.2 Apr 25, 2023
0.6.0 Apr 15, 2023
0.5.2 Apr 15, 2023
0.1.1 May 30, 2019

#647 in Network programming

Download history 3/week @ 2024-02-18 8/week @ 2024-02-25 1/week @ 2024-03-03 9/week @ 2024-03-10 74/week @ 2024-03-31 1/week @ 2024-04-07

75 downloads per month
Used in door-macros

MPL-2.0 license

790 lines

Rusty Doors

The goal of this crate is to expose the illumos Doors API in Rust. It exposes the native doors API verbatim, and also provides some moderately safer abstractions.

What are Doors?

A door is a file-like mechanism for interprocess communication, not unlike a named pipe or a UNIX Domain Socket. Client programs can invoke functions (called server procedures) in door servers if the door server has made a door available on the filesystem.

A server procedure is a function within the door server program that has a special, predefined signature. It is the entrypoint for the thread that is created (or awoken) to handle a client's door invocation.

A door server is a process that has created a door from one of its server procedures.


A server procedure that simply doubles its input might look like this:

use doors::server::Door;
use doors::server::Request;
use doors::server::Response;

fn double(x: Request) -> Response<[u8; 1]> {
  if x.data.len() > 0 {
    return Response::new([x.data[0] * 2]);
  } else {
    // We were given nothing, and 2 times nothing is zero...
    return Response::new([0]);

let door = Door::create(double).unwrap();

A client program which invokes that server procedure might look something like this:

use doors::Client;

let client = Client::open("/tmp/double.door").unwrap();

let response = client.call_with_data(&[111]).unwrap();
assert_eq!(response.data()[0], 222);



~35K SLoC