Skip to content

Requests may have non-sequential stream ids #749

@mostroverkhov

Description

@mostroverkhov

Happens when request (for all interactions) subscriptions race

RequestResponseFrameFlyweight.encode(
- so frames are sent not in same order as stream ids are created
int streamId = streamIdSupplier.nextStreamId(receivers);
. Other than being against spec this makes implementing http2 streams transport harder that necessary - http2 request stream ids are strictly sequential also as I cant trust rsocket stream ids. Just for discussion - will have reproducer by the end of the week.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugsupersededIssue is superseded by another

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions