Detaching Socket from HTTPSession

Question

Detaching Socket from HTTPSession

Opened this issue 2 months ago · 4 comments

SteveSelva commented 2 months ago

Is there any safe way to detach folly::AsyncTransport from proxygen::HTTPSession without closing the socket?

Answer 1 · 2024-11-06T17:34:30.000Z

I don't think there's currently a way to do this

Answer 2 · 2024-11-07T04:59:52.000Z

Is there any possibility of implementing this in future?

Answer 3 · 2024-11-22T22:19:06.000Z

What is it you are trying to do? Pass the underlying AsyncSocket off after an HTTP/1.x CONNECT?

Could you instead write an AsyncTransport implementation that uses HTTPTransaction/Handler to send/receive data? This has the benefit of working with HTTP/2 and 3 also.

Answer 4 · 2024-11-27T05:51:23.000Z

After HTTP CONNECT, I am planning to detach the folly::AsyncTransport from the HTTPSession, and then just forward the data from both ends. And I have optimized that forwarding code similar to HTTPSession, where writes are sent at the end of each event base loop. And also control the amount of data that can be read over a single event base loop. I am stuck at detaching the AsyncTransport from HTTPSession.

Can you provide any example code for implementation of AsyncTransport that uses HTTPTransaction/Handler.