My application will depend, unfortunately, on a device that can’t be reverse engineered. Its modus operandi is having a dongle/app combo that acts like a proxy, getting (Bluetooth) messages from the device, sending to the server, getting a response from the server, sending that to the device. This is the only way I know to keep the device synced to their proprietary database, and our organization is committed to this device/vendor. The connection from the dongle/app to their proprietary server is SSL (https, but not REST). Messages are small and few, then the session shuts down. Number of sessions per day is low, so it’s a good Dash candidate.
My question is this, how to get the Dash to act like this proxy app? It’s unclear reading the docs that this is a good fit for the proposed API. So is the only alternative to write my own server that is a proxy, encapsulate into REST communication, and then use the Konekt API to do REST with my server? My server would have to extract the data and establish a session to the device’s normal server (with appropriate credentials) in order to obtain the needed response for the REST transaction.
Is my understanding correct, or is there some way to directly make an HTTPS connection (tcp/ip to port 443) without having to write my own server?