You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using a library that generates connections as supervisors because there's multiple processes to manage the connection. Technically, the connection is a child of the supervisor, but every function that expect a process to be passed to it, expects the supervisor. Thus, I'd like to manage a pool of supervisors instead of workers. The problem I ran into is that poolboy's child_spec function will only create workers. I've worked around this by defining my own child spec. However, this seems plausible as something others would want to do.
One question I have is, is this a horrible idea because of something inherent to the way poolboy works?
If it's not, I'd be happy to contribute this feature.
The text was updated successfully, but these errors were encountered:
I'm using a library that generates connections as supervisors because there's multiple processes to manage the connection. Technically, the connection is a child of the supervisor, but every function that expect a process to be passed to it, expects the supervisor. Thus, I'd like to manage a pool of supervisors instead of workers. The problem I ran into is that poolboy's
child_spec
function will only create workers. I've worked around this by defining my own child spec. However, this seems plausible as something others would want to do.One question I have is, is this a horrible idea because of something inherent to the way poolboy works?
If it's not, I'd be happy to contribute this feature.
The text was updated successfully, but these errors were encountered: