Hi Nicholas,
Today, I see in the current implementation there is two flows which is
used : one for screen and an other one for control. Each flow use
their own socket (screen Socket and control Socket). The problem is
that the request for next screen is send on the control socket and the
response is send back on the screen socket (correct me if I'm wrong).
So this will not be easy to setup an HTTP tunneling when the request/
response is not made on the same socket. I think the current design
should be sligthly changed in order to do the request/response of the
screen frame on the same socket. In that way, the HTTP GET/HTTP 200 OK
will be used on the screen flow and the only HTTP POST/HTTP 200
OK(empty body) model can be used on the control flow.
My question is to know your though about that and also the amount of
work to change the request/response model inside the client/server
code
Best regards
Shan