Skip to content

Expose some functions for async users who accepts the connection themselves - #147

Merged
haraldh merged 2 commits into
varlink:masterfrom
RaitoBezarius:master
Jul 23, 2026
Merged

Expose some functions for async users who accepts the connection themselves#147
haraldh merged 2 commits into
varlink:masterfrom
RaitoBezarius:master

Conversation

@RaitoBezarius

Copy link
Copy Markdown
Contributor

Fixes #146.

The rationale is described in commit messages but it boils down to: it's very hard to accept connections yourselves and reuse these logic.

Users who want to follow the same logic that the library does while
handling socket activation themselves could benefit from having this
function pub.

Signed-off-by: Raito Bezarius <masterancpp@gmail.com>
End users who are manipulating the stream themselves can benefit from
calling these functions themselves and handling the I/O.

Signed-off-by: Raito Bezarius <masterancpp@gmail.com>
@haraldh haraldh closed this Jul 23, 2026
@haraldh haraldh reopened this Jul 23, 2026
@haraldh
haraldh merged commit b733583 into varlink:master Jul 23, 2026
10 of 14 checks passed
@haraldh

haraldh commented Jul 23, 2026

Copy link
Copy Markdown
Collaborator

I am sorry.. I am a bad maintainer... didn't check the repos

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.

Make AsyncStream methods public and handle_connection public

2 participants