slawlor / ractor_actors

Common utility actors built with Ractor

Hi, I'm Sean and I'm a Rustacean.

About me

I'm currently a software engineer at Meta Platforms in Core Systems. I work on distributed, high-throughput systems.

Selected repos

1. ractor - Inspired by Erlang's OTP, ractor provides save actor programming paradigms in 100% Rust.
2. akd - Auditable Key Directories (AKDs) are the foundation of Key Transparency at WhatsApp. This is the core logic for WhatsApp's realization.

ractor_actors's Issues

Create initial utility actors

Moved from slawlor/ractor#45 to independent repo

We have a gen_server equivalent (basic actor), now we can expand on that

• factory for a pool of workers local to a node #46 , #47

Other possible utility actors that might be helpful to have:

• Timer (execute on a period ignore comp time, execute on a period handling comp time taking too long, execute with a delay between, etc)
• FileWatcher? Watch a specified file (or directory) and notify someone on changes (output-port use case?)
• Basic networking [tcp/udp] servers and clients? This however might require enforcing some kind of encoding (i.e. length pre-pended frames) or something

Examples for TCP networking

Would love to see some examples of the actors here, specifically the listener actor.

I'm a little stuck on how to spawn the actor, and setting up the SessionAcceptor. I'm coming from actix with a use case of processing bincode data over the wire from TCP streams. I was previously using actix_server::Server to spawn a server which listens and then handles each incoming stream which then forwards the decoded data as a struct to another actor for further processing.

Any help would be greatly appreciated. TIA 😄