ntl/actor

Actor pattern implementation for ruby

actor's Issues

Offer the ability to subscribe to all messages sent to supervisor

Prepend a build method on Actor that calls configure

• Implement build class method. Use Module#prepend to allow specializations. Allow arbitrary arguments.
• Remove check for build method : https://github.com/ntl/actor/blob/master/lib/actor/build.rb#L19-L23

Rack integration

• Minimal rack application that exposes a interface for pause, resume and start commands sent as HTTP POST requests.
• Web server (i.e. webrick) can be selected by end user
• Interface for handling actor messages from e.g. eventide consumers. Useful for collecting statistics for display
• Interface for allowing e.g. eventide consumers to get an address to send telemetry via actor messages
• Documentation

Class actuators for actors should accept single arguments

address, thread = SomeActor.start include: :thread

Rename Write to Send

Name of actor class should be included in status update

Replace use of threads with Ractor

Build method needs to call configure

https://github.com/ntl/actor/blob/master/lib/actor/build.rb#L31

Supervisor messages sent to actors need to "cut" the line

It's possible for thousands of messages to be queued up when an actor is sent the stop message. The supervisor must be able to send a priority message.

Supervisor should not need the thread

Instead, #spawn should be used by actor assembly code in order to ensure that the thread that was spawned shows up in the supervisor's thread group.

Actor::Start causes problems for supervisor

1. Supervisors should not rescue errors and send an actor crashed notification
2. When starting a supervisor, an actor started message should not get sent to the supervisor

Improve the behavior of `Actor.start` when supervisor is not running

Perhaps call thread.join.