Re: [libmicrohttpd] Protocol upgrade

[Markus Doppelbauer]

Dear Evgeny,
> The best what MHD could do with "upgraded" sockets - is
> to forward data to application and back to remote.
Yes - as much as data until the socket blocks. And it
should hide everything else from the application, e.g.
"sha1('Sec-WebSocket-Accept')".
Is is easy to figure out, whether the the data contains
half of a request or multiple requests.
I don't know about others, but we need only the server-side
counterpart to the javascript "new WebSocket(url)".
Thanks a lot!
Markus

Am Montag, den 14.11.2016, 15:35 +0300 schrieb Evgeny Grin:
> Dear Markus,
> 
> It's clear how to use this logic for HTTP connections.
> But application may use any arbitrary protocol for "upgraded" sockets
> so
> MHD doesn't know what should be interpreted as "request"(if word
> "request" is applicable for protocol). The best what MHD could do
> with
> "upgraded" sockets - is to forward data to application and back to
> remote.
> That's implemented currently. For TLS connections, MHD hides all
> TLS-related machinery and provides plain socket for application.
> 
> Not sure that I get idea about "pipe() on TLS". Could you explain it
> a
> little?
>