You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: