Skip to content

Conversation

@mechite
Copy link
Contributor

@mechite mechite commented Nov 8, 2025

Clarify that virtual threads aren't just a default or suggestion,
but a hard requirement.

Related-to: #320 (comment)
Signed-off-by: Mahied Maruf contact@mechite.com

Clarify that virtual threads aren't just a default or suggestion,
but a hard requirement.

Related-to: avaje#320 (comment)
Signed-off-by: Mahied Maruf <contact@mechite.com>
@SentryMan
Copy link
Collaborator

Probably better to say that we lack async in favor of virtual threads

Related-to: avaje#321 (comment)
Signed-off-by: Mahied Maruf <contact@mechite.com>
@rbygrave
Copy link
Contributor

rbygrave commented Nov 9, 2025

I'd probably just leave the docs as is personally.

no Future-based programming model

People can actually do whatever they like with the request handling ... it's more that jex is just the ExecutorService executing the request/response [without any event loop / async nio etc] and that defaults to using Virtual Threads. I think trying to say that as "no Future-based programming model" isn't making that clearer and in fact will confuse some people.

@mechite mechite closed this Nov 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants