-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Direct-style websockets with Eio #130
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know anything about web-sockets, but the Eio stuff looks reasonable to me. I suspect you don't need most of the Buf_write.flush
calls, though. The buffer gets flushed automatically when you block; flush
just makes the caller wait until the data has finished flushing but doesn't speed it up (any more than calling Fiber.yield ()
would, anyway).
Is there anything holding back this PR for merge? Anything I can perhaps do to help push it over the line? |
Thanks for the interest and offer for help @ryanslade. I would say this PR is blocked on landing a proper release of cohttp-eio. Right now, it is an |
Hi. Cohttp 6.0.0~beta1 is out and it has |
I tried to build this PR with cohttp-eio.6.0.0~alpha2 but stuck with compilation error.
@patricoferris have things become better in last year? |
Quickly bump to work with cohttp-eio.6.0.0~beta2 should make this work with the |
This PR adds direct-style websockets using eio and cohttp-eio (yet unreleased, but it has been merged in the main branch of mirage/ocaml-cohttp). It is WIP and probably will change, but I thought I would open this PR in case I don't have time to come back to it later.
cc: @bikallem @talex5 who might be able to comment on the core IO implementation a little :))