Open jhvanderven opened 7 years ago
I think it is because browsers use a newer websocket protocol (but I don't have to time to update it now)
2017-05-03 13:29 GMT+02:00 Johnny H. notifications@github.com:
Hi Andre,
Thanks for creating something that I think should be part of the RemObjects library. We have a client server solution using RemObjects' supertcp or superhttp. We now want to move to browser based clients, but do not want to lose the two-way communication and definitely want to avoid polling in the client.
I have been trying to get the examples to work on Delphi 10.2 but I have not succeeded in getting my target architecture to work. The Delphi client/delphi server setup works, but when I use a browser client, the first call to the server never completes. I get the expected 101 response and then the Network tab of Chrome says: CAUTION: Request is not finished yet. And that remains so forever.
Do you have an idea what could be causing this?
I am using the TROIndyHTTPWebsocketServer, because we need something derived from ROServer.
Kind regards,
Jan
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/andremussche/DelphiWebsockets/issues/26, or mute the thread https://github.com/notifications/unsubscribe-auth/AC5Ijprem2BnGS7air4max9lCOhMZnBpks5r2GUVgaJpZM4NPRIS .
Hi Andre,
Thanks for creating something that I think should be part of the RemObjects library. We have a client server solution using RemObjects' supertcp or superhttp. We now want to move to browser based clients, but do not want to lose the two-way communication and definitely want to avoid polling in the client.
I have been trying to get the examples to work on Delphi 10.2 but I have not succeeded in getting my target architecture to work. The Delphi client/delphi server setup works, but when I use a browser client, the first call to the server never completes. I get the expected 101 response and then the Network tab of Chrome says: CAUTION: Request is not finished yet. And that remains so forever.
Do you have an idea what could be causing this?
I am using the TROIndyHTTPWebsocketServer, because we need something derived from ROServer.
Kind regards,
Jan