Skip to content
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

a standalone version of neverbleed #44

Open
rock59 opened this issue Jan 10, 2023 · 0 comments
Open

a standalone version of neverbleed #44

rock59 opened this issue Jan 10, 2023 · 0 comments

Comments

@rock59
Copy link

rock59 commented Jan 10, 2023

I am developling a proxy server using Golang and a modified version of h2o and libh2o-evloop. I modify h2o and build it as a static library with every h2o new commit to keep current with it. Everythings work fine till 0f08b67. I simply strip out neverbleed related codes from h2o because Golang runtime is not fork() friendly without exec (neverbleed uses fork() without exec ) . But as of 0f08b67, it seems that quicly uses neverbleed for async resumption and I cant simply strip out neverbleed related codes from h2o to make it work fine.

Neverbleed is awesome library and it would be nice to provide a standalone version of neverbleed with a main() entry so developers interesting in neverbleed can use it with fork/exec or h2o_spawn or similar mechanism in their projects.

thanks

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

No branches or pull requests

1 participant