Skip to content

Consider a different concurrency model for the framework #115

Open
@coryan

Description

@coryan

The framework currently uses "thread-per-connection" concurrency model. This was simple to implement, but may not be what we want as it places no practical limits on the number of threads and connections.

We may want to consider something like a fixed thread-pool. I am partial to the Leader/Followers Pattern (obviously), but a single thread for I/O and a thread-pool to handle each request could be made to work too.

Only once we have decided on the threading model does it make sense to talk about controlling the thread pool sizes as discussed in #25

Metadata

Metadata

Assignees

No one assigned

    Labels

    type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions