Skip to content

InvocationType improvements and cleanups #12266

@sbordet

Description

Jetty version(s)
12

Description
On the server, the InvocationType of a Handler controls how Jetty invokes the Handler chain.

On the client, instead, the InvocationType is hardcoded to be BLOCKING for HTTP/1.1, a mix of undefined, BLOCKING and NON_BLOCKING for HTTP/2 and HTTP/3.

There should be an option on the client to allow applications to specify the invocation type, with consistent defaults across transports if not specified.

With the occasion, we should also get rid of the deprecated AbstractConnection.getInvocationType().

Metadata

Assignees

Labels

BugFor general bugs on Jetty side

Type

No type

Projects

  • Status

    ✅ Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions