-
Notifications
You must be signed in to change notification settings - Fork 74
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
Different behavior between nqsb-tls and openssl #97
Comments
All of this with conduit 0.9.0, cohttp 0.18.0, tls 0.6.0. |
I just tried with the new TLS release and the lack of concurrency is still there:
|
rgrinberg
added a commit
to rgrinberg/ocaml-conduit
that referenced
this issue
Dec 12, 2015
Server in `Conduit_lwt_tls` waits for a user callback to finish before accepting more connections. Instead, it should only wait until the connection is accepted and detach the client callback Fix mirage#97
rgrinberg
added a commit
to rgrinberg/ocaml-conduit
that referenced
this issue
Dec 12, 2015
Server in `Conduit_lwt_tls` waits for a user callback to finish before accepting more connections. Instead, it should only wait until the connection is accepted and detach the client callback Fix mirage#97
@rgrinberg It works (I did |
rgrinberg
added a commit
to rgrinberg/ocaml-conduit
that referenced
this issue
Dec 21, 2015
Server in `Conduit_lwt_tls` waits for a user callback to finish before accepting more connections. Instead, it should only wait until the connection is accepted and detach the client callback Fix mirage#97
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Maybe I'm missing something obivous, but with
CONDUIT_TLS=native
the HTTP requests seems to be handled sequentially.This is my server:
OpenSSL
If I run
CONDUIT_TLS=openssl ocaml server.ml
Then I can run
curl -k https://127.0.0.1:4242/sleep
on one terminal, and many timescurl -k https://127.0.0.1:4242/hello
on another terminal, everything is fine.OCaml-TLS
When running
CONDUIT_TLS=native ocaml server.ml
, if I havecurl -k https://127.0.0.1:4242/sleep
on one shell, any call tocurl -k https://127.0.0.1:4242/hello
on another terminal will block until the/sleep
is done.The text was updated successfully, but these errors were encountered: