arkOS: DelugeDNS Design

# DelugeDNS Design

## Complete Flow of Deluge+/Deluge Direct/$name

1. User installs arkOS

2. User pays $3/month for Deluge Direct or whatever it's called so they don't have to open up a router port to benefit from Deluge
and gets an authentication token as part of that process

3. User types that auth token into the Deluge plugin for Genesis

4. A Deluge client built into arkOS does an API call to the Deluge server, initiating a WebSocket connection that remains open
suppose this user's chosen subdomain is user1.arkos.io

5. A totally different user tries to visit http://user1.arkos.io/

6. DNS resolves to the Deluge server, which then sees that user1's RPi is connected via WebSocket and should receive the request

7. Deluge then performs said HTTP request (to user1.arkos.io) on behalf of the "totally different user" -- say, visitor1 -- over the existing WebSocket
(06:48:26 PM) ArturoVM: Now comes the tricky part, I'm guessing.

8. The Deluge client built into arkOS that is handling the WebSocket connection gets the request, then does an actual HTTP request to the local machine at the requested URL (in this case, "/", the home page)

9. The Deluge client then receives that response and sends it via the existing WebSocket connection to Deluge

10. Deluge (the Deluge server) then forwards that response data to visitor1

---

The JSON would look like this:

{"url": "/admin/foo/bar", "method": "GET", "headers": {"User-Agent": "...", "Host": "...", "Accept": "..."}}

...or possibly more like this:

{"protocol":"http", "port":80, "data":"GET /... "}