Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Provide an asynchronous IO API for actors #52

Closed
Neverlord opened this Issue · 2 comments

2 participants

@Neverlord
Owner

Scheduled actors, both context-switching and event-based, shall not use blocking systems calls such as read/write/select. Thus, actors are of very limited use if it comes to IO, since only thread-mapped actors can do IO without starving others. We therefore need a message-based (?) asynchronous IO layer for actors.

@mavam
Collaborator

I actually was about to write an event-based actor which performs read/write/select to communicate over a custom transport protocol. So I'd be curious to see how you would wrap these low-level functionality. I've been using Boost Asio for a while, which may be a good source for inspiration when it comes to asynchronous design.

@Neverlord
Owner

This feature has been implemented in 0.8 as broker actors.

@Neverlord Neverlord closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.