Skip to content
This repository has been archived by the owner on Sep 3, 2024. It is now read-only.

Move next_stream_idto ConnectionContext #86

Open
TimEvens opened this issue Nov 21, 2023 · 0 comments
Open

Move next_stream_idto ConnectionContext #86

TimEvens opened this issue Nov 21, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@TimEvens
Copy link
Contributor

Currently next_stream_id is at the transport class scope. This is fine for clients, but it's not really ideal for servers. Moving this to ConnectionContext will make this connection specific, which is what it should be.

When moving it should be renamed to last_stream_id since it's really the last stream number assigned, not the next one available. This is used to feed it back into make_stream_id()

@TimEvens TimEvens added the enhancement New feature or request label Nov 21, 2023
@TimEvens TimEvens assigned TimEvens and unassigned TimEvens Nov 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant