Contexts AThread?

[rlebeau]

So a thread could handle multiple tasks (whatever a task is meant to be lol)

In this case, a task is a client context (TIdContext derives from TIdTask). But the API was abstracted so in theory it could be used for other purposes.

and a task could be handled across multiple threads. A context could be passed between multiple threads and multiple threads could pass around a context.

That was the plan, but it never materialized that way.

but a thread pool has threads that can handle multiple tasks.

Yes. When a thread is done with a task, the thread can go back in the pool until a new task is ready for it.

That being said, the pooling is not the default behavior. You have to use the TIdSchedulerOfThreadPool component to get the behavior.