04-28-2022, 12:14 AM
Thanks for the help and quick response.
The reason I am using Http is that I am registering the client first for the connection with a POST request that will be sent once. That request will have only small data like user id and current status "Connected" or anything else indicating that the that specific client is online.
So, as I mentioned before I am forced to use HTTP because of the structure of this web server framework that we have. I didn't want to have another TCP server in the host app just for the sake of if ever I needed one in a similar case.
I am not trying to abuse any protocols here I am just trying to use the minimum resources as possible, in the worst case scenario I could put a TCP server inside the dll and connect to it from client. I just thought that there might be away to use the already existing server in the host app.
The reason I am using Http is that I am registering the client first for the connection with a POST request that will be sent once. That request will have only small data like user id and current status "Connected" or anything else indicating that the that specific client is online.
So, as I mentioned before I am forced to use HTTP because of the structure of this web server framework that we have. I didn't want to have another TCP server in the host app just for the sake of if ever I needed one in a similar case.
I am not trying to abuse any protocols here I am just trying to use the minimum resources as possible, in the worst case scenario I could put a TCP server inside the dll and connect to it from client. I just thought that there might be away to use the already existing server in the host app.