CODEWITHSUNDEEP
erlangerlang-otpelixir
Derek Chiang
Derek Chiang

Reputation: 3410

How to fit non-event driven processes into supervision tree?

I want to be able to spawn a lot of processes that process data and fit them into a supervision tree. However all default behaviours, namely gen_server, gen_fsm, and gen_event, are event-driven. They have to receive messages to do stuff. What I need are just processes that process data, and in case they terminate abnormally, they should be restarted by their supervisor. What's the best way to go about doing this?

Upvotes: 0

Views: 176

Answers (1)

rvirding
rvirding

Reputation: 20926

Yes, the standard behaviours all function as servers in that they sit and wait for requests before they do something. However, OTP is open in the sense that it provides the tools you need to implement processes which are not behaviours but which fit into the supervision trees and do "the right thing". For a description on what needs to be done and how to do it see the section on Special processes in the Erlang documentation.

This is really not surprising as all of OTP behaviours are implemented in Erlang so all the "tools" are there in the libraries.

Upvotes: 1

Related Questions