To eventually support TLS connections through the app, we need a HTTP server running inside the app that handles the backend FlyWeb semantics - namely providing custom TLS authentication for FlyWeb services viewed via an Android WebView.
The basic design I'm thinking of is to use a single NIO thread to poll all the IO options. The IO sources managed are:
Server socket on loopback port, to service incoming requests from webview.
listen for accept() events, and add new client socket.
Local socket for every active connection
listen for read() and write() from web view requests.
Remote socket for every active connection
listen for read() and write() from service webserver
For now, we can worry about just forwarding plain HTTP requests, and leave the TLS handling for later.
To eventually support TLS connections through the app, we need a HTTP server running inside the app that handles the backend FlyWeb semantics - namely providing custom TLS authentication for FlyWeb services viewed via an Android WebView.
The basic design I'm thinking of is to use a single NIO thread to poll all the IO options. The IO sources managed are:
For now, we can worry about just forwarding plain HTTP requests, and leave the TLS handling for later.